Digital Paint Discussion Board
Paintball 2: The Game => Server Discussion => Topic started by: jitspoe on March 28, 2007, 07:57:22 PM
-
I thought I made a post about this before, but I couldn't find it. It might have been in the month of data that was lost. Anyway, after the recent lag issues with the EV1 servers, I'm considering switch servers again. EV1 has merged with The Planet, so it's still sort of the same, but I think it would be located in a different data center (hopefully one that doesn't have the laggy routing issue). I've been hesitant to do this before because the ping to the EV1 servers has always been a good 10-20% lower than the Graffiti Paint servers (which are hosted by The Planet). It doesn't do much good, though, if they only work well for me. I also think it's a good idea to have servers in as many different locations as possible, even if it's just different data centers within the same state.
Pros:
+ Hopefully resolves lag issue some players are having.
+ Newer OS (CentOS 4 vs RHES 3).
+ Cheaper if I get the package without support.
Cons:
- Possibly higher ping.
- Extra time and effort to move everything I've done over to the new server.
- Transition of domains and such might cause issues for a few days.
-
How about you scrap those and get some located in Europe!
-
altough there have been more and more euro users playing this game i think there are still more na so if jits has to choose from na or euro he will choose na...
so for now i think we`ll be pubbing at otbs and ur new server too ;)
-
is the planet still the best, or what other options are there. i dont have any problems with EV1 so i would say go for the cheaper one, then go buy yourself something nice.
-
I also think it's a good idea to have servers in as many different locations as possible, even if it's just different data centers within the same state.
Do you know any of the locations of the prospective servers?
-
I've been hesitant to do this before because the ping to the EV1 servers has always been a good 10-20% lower than the Graffiti Paint servers (which are hosted by The Planet).
Rotflmao Are you kidding me?? Lower than the GRaFFiTi servers to YOU maybe but overall the GRaFFiTi servers are and have been for what, a year and a half, the most stable and longest lasting DP servers in existence.
I am surprised you are able to get servers from "The Planet" but that's another story. If you can, then make sure you give the servers an attractive name.
-
not a bad idea
:]
-
Well, let's do this, then. Ping both EV1 and GP. I'm curious how it varies for different people. This is what I get:
EV1:
Pinging dplogin.com [216.127.68.86] with 32 bytes of data:
Reply from 216.127.68.86: bytes=32 time=35ms TTL=46
Reply from 216.127.68.86: bytes=32 time=38ms TTL=46
Reply from 216.127.68.86: bytes=32 time=36ms TTL=46
Reply from 216.127.68.86: bytes=32 time=35ms TTL=46
Graffiti Paint:
Pinging 69.93.11.66 with 32 bytes of data:
Reply from 69.93.11.66: bytes=32 time=44ms TTL=45
Reply from 69.93.11.66: bytes=32 time=44ms TTL=45
Reply from 69.93.11.66: bytes=32 time=44ms TTL=45
Reply from 69.93.11.66: bytes=32 time=44ms TTL=45
It's typically 5-10ms higher at graffiti. Not a huge difference, and they're both good, but EV1 is slightly better (for me).
-
Again not only is this you pinging the servers from your own machine, you proved 2 points:
1. There is very very little difference, definately NOT a noticable difference with the ping times between the 2 servers but more importantly...
2. GRaFFiTi's pings are ALL identical and consistant proving stability.
Lastly, getting servers with "The Planet" is positively a productive choice.
-
Nah, that was just chance. If I ping it again...
Pinging 69.93.11.66 with 32 bytes of data:
Reply from 69.93.11.66: bytes=32 time=63ms TTL=45
Reply from 69.93.11.66: bytes=32 time=43ms TTL=45
Reply from 69.93.11.66: bytes=32 time=43ms TTL=45
Reply from 69.93.11.66: bytes=32 time=43ms TTL=45
Anyway, I already have a server with The Planet, since EV1 and The Planet merged. My bills say "The Planet" on them. I'd just be getting a different machine with potentially different routing.
-
OK Guys....
Just pinging a server with standard sized packets really won't show any issues.
When I get to the office, I'll run some tests with ping-a-chu variable size packet attacks ( a tribute to Sad here), well at least some off size packets and see what happens.
jit, do you know how big the datagrams are that dp uses to communicate with the servers? Knowing that might help be as realistic as possible.
-
jit, do you know how big the datagrams are that dp uses to communicate with the servers? Knowing that might help be as realistic as possible.
Up to 1400 bytes.
-
Ping to DPLogin
Pinging 216.127.68.86 with 1400 bytes of data:
Reply from 216.127.68.86: bytes=1400 time=42ms TTL=52
Reply from 216.127.68.86: bytes=1400 time=40ms TTL=52
Reply from 216.127.68.86: bytes=1400 time=40ms TTL=52
Reply from 216.127.68.86: bytes=1400 time=40ms TTL=52
Ping to GP Servers
Pinging 69.93.11.66 with 1400 bytes of data:
Reply from 69.93.11.66: bytes=1400 time=37ms TTL=51
Reply from 69.93.11.66: bytes=1400 time=34ms TTL=51
Reply from 69.93.11.66: bytes=1400 time=34ms TTL=51
Reply from 69.93.11.66: bytes=1400 time=35ms TTL=51
-
Ping to DPLogin
Ping wird ausgeführt für 216.127.68.86 mit 32 Bytes Daten:
Antwort von 216.127.68.86: Bytes=32 Zeit=184ms TTL=48
Antwort von 216.127.68.86: Bytes=32 Zeit=183ms TTL=48
Antwort von 216.127.68.86: Bytes=32 Zeit=188ms TTL=51
Antwort von 216.127.68.86: Bytes=32 Zeit=185ms TTL=48
Ping to GT Servers
Ping wird ausgeführt für 69.93.11.66 mit 32 Bytes Daten:
Antwort von 69.93.11.66: Bytes=32 Zeit=182ms TTL=51
Antwort von 69.93.11.66: Bytes=32 Zeit=183ms TTL=51
Antwort von 69.93.11.66: Bytes=32 Zeit=184ms TTL=51
Antwort von 69.93.11.66: Bytes=32 Zeit=185ms TTL=51
They are the same for me (prolly for most of EU players).
-
DPlogin
A enviar para 216.127.68.86 com 32 bytes de dados:
Resposta de 216.127.68.86: bytes=32 tempo=155ms TTL=44
Resposta de 216.127.68.86: bytes=32 tempo=156ms TTL=44
Resposta de 216.127.68.86: bytes=32 tempo=160ms TTL=44
Resposta de 216.127.68.86: bytes=32 tempo=160ms TTL=44
GT
A enviar para 69.93.11.66 com 32 bytes de dados:
Resposta de 69.93.11.66: bytes=32 tempo=153ms TTL=47
Resposta de 69.93.11.66: bytes=32 tempo=170ms TTL=47
Resposta de 69.93.11.66: bytes=32 tempo=156ms TTL=47
Resposta de 69.93.11.66: bytes=32 tempo=157ms TTL=47
yep..its about the same...
-
Pinging 216.127.68.86 with 32 bytes of data:
Reply from 216.127.68.86: bytes=32 time=196ms TTL=43
Reply from 216.127.68.86: bytes=32 time=165ms TTL=44
Reply from 216.127.68.86: bytes=32 time=166ms TTL=43
Reply from 216.127.68.86: bytes=32 time=165ms TTL=44
Pinging 69.93.11.66 with 32 bytes of data:
Request timed out.
Reply from 69.93.11.66: bytes=32 time=150ms TTL=43
Reply from 69.93.11.66: bytes=32 time=151ms TTL=42
Reply from 69.93.11.66: bytes=32 time=151ms TTL=43
GT ftw! :)
-
EV1
Antwort von 216.127.68.86: Bytes=32 Zeit=181ms TTL=50
Antwort von 216.127.68.86: Bytes=32 Zeit=182ms TTL=50
Antwort von 216.127.68.86: Bytes=32 Zeit=182ms TTL=50
Antwort von 216.127.68.86: Bytes=32 Zeit=182ms TTL=50
GT
Antwort von 69.93.11.66: Bytes=32 Zeit=190ms TTL=52
Antwort von 69.93.11.66: Bytes=32 Zeit=190ms TTL=52
Antwort von 69.93.11.66: Bytes=32 Zeit=190ms TTL=52
Antwort von 69.93.11.66: Bytes=32 Zeit=190ms TTL=52
:)
-
Packets are hardly ever close to 1400 -- that's just the absolute max. Can't hurt to check for worst case, though...
C:\Documents and Settings\jitspoe>ping -l 1400 dplogin.com
Pinging dplogin.com [216.127.68.86] with 1400 bytes of data:
Reply from 216.127.68.86: bytes=1400 time=42ms TTL=46
Reply from 216.127.68.86: bytes=1400 time=43ms TTL=46
Reply from 216.127.68.86: bytes=1400 time=43ms TTL=46
Reply from 216.127.68.86: bytes=1400 time=40ms TTL=46
Ping statistics for 216.127.68.86:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 43ms, Average = 42ms
C:\Documents and Settings\jitspoe>ping -l 1400 69.93.11.66
Pinging 69.93.11.66 with 1400 bytes of data:
Reply from 69.93.11.66: bytes=1400 time=48ms TTL=45
Reply from 69.93.11.66: bytes=1400 time=48ms TTL=45
Reply from 69.93.11.66: bytes=1400 time=47ms TTL=45
Reply from 69.93.11.66: bytes=1400 time=46ms TTL=45
Ping statistics for 69.93.11.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 48ms, Average = 47ms
I guess I can shell out an extra $100 for one month to test out the new server and see how it runs. I need to make this decision before I release build 18 and people become dependant on the login system.
-
Considering the possible socket blocking problem, if this is a possible issue with the EV1 server then it might be a better plan to go with The Planet.
-
Pinging 216.127.68.86 with 32 bytes of data:
Reply from 216.127.68.86: bytes=32 time=148ms TTL=51
Reply from 216.127.68.86: bytes=32 time=150ms TTL=51
Reply from 216.127.68.86: bytes=32 time=150ms TTL=51
Reply from 216.127.68.86: bytes=32 time=150ms TTL=51
Pinging 69.93.11.66 with 32 bytes of data:
Reply from 69.93.11.66: bytes=32 time=141ms TTL=51
Reply from 69.93.11.66: bytes=32 time=142ms TTL=51
Reply from 69.93.11.66: bytes=32 time=141ms TTL=51
Reply from 69.93.11.66: bytes=32 time=141ms TTL=51
GT for me too
-
I'm in the process of trying to get a new server set up with them now. We'll see how it goes.
-
i hope with the coming of this new server will ease to your work jits.
good luck
-
I'm in the process of getting the new server ordered.
-
GT edged it out by a very slight margin.
-
The new server is getting set up.
Old EV1 server:
Pinging dplogin.com [216.127.68.86] with 32 bytes of data:
Reply from 216.127.68.86: bytes=32 time=37ms TTL=46
Reply from 216.127.68.86: bytes=32 time=38ms TTL=46
Reply from 216.127.68.86: bytes=32 time=39ms TTL=46
Reply from 216.127.68.86: bytes=32 time=40ms TTL=46
New ThePlanet server:
Pinging 70.85.9.178 with 32 bytes of data:
Reply from 70.85.9.178: bytes=32 time=57ms TTL=46
Reply from 70.85.9.178: bytes=32 time=54ms TTL=46
Reply from 70.85.9.178: bytes=32 time=57ms TTL=46
Reply from 70.85.9.178: bytes=32 time=56ms TTL=46
-
Antwort von 216.127.68.86: Bytes=32 Zeit=182ms TTL=50
Antwort von 216.127.68.86: Bytes=32 Zeit=182ms TTL=50
Antwort von 216.127.68.86: Bytes=32 Zeit=179ms TTL=50
Antwort von 216.127.68.86: Bytes=32 Zeit=181ms TTL=50
Antwort von 70.85.9.178: Bytes=32 Zeit=242ms TTL=54
Antwort von 70.85.9.178: Bytes=32 Zeit=270ms TTL=54
Antwort von 70.85.9.178: Bytes=32 Zeit=278ms TTL=54
Antwort von 70.85.9.178: Bytes=32 Zeit=246ms TTL=54
-
Not looking too hot so far. Maybe I need to just see if I can get the lag spike issues resolved on the old EV1 server.
-
Pinging 216.127.68.86 with 32 bytes of data:
Reply from 216.127.68.86: bytes=32 time=70ms TTL=49
Reply from 216.127.68.86: bytes=32 time=70ms TTL=49
Reply from 216.127.68.86: bytes=32 time=71ms TTL=49
Reply from 216.127.68.86: bytes=32 time=69ms TTL=49
Pinging 70.85.9.178 with 32 bytes of data:
Reply from 70.85.9.178: bytes=32 time=83ms TTL=48
Reply from 70.85.9.178: bytes=32 time=82ms TTL=48
Reply from 70.85.9.178: bytes=32 time=81ms TTL=48
Reply from 70.85.9.178: bytes=32 time=81ms TTL=48
-
Pinging 216.127.68.86 with 32 bytes of data:
Reply from 216.127.68.86: bytes=32 time=71ms TTL=48
Reply from 216.127.68.86: bytes=32 time=49ms TTL=48
Reply from 216.127.68.86: bytes=32 time=39ms TTL=48
Reply from 216.127.68.86: bytes=32 time=53ms TTL=48
Pinging 70.85.9.178 with 32 bytes of data:
Reply from 70.85.9.178: bytes=32 time=72ms TTL=50
Reply from 70.85.9.178: bytes=32 time=39ms TTL=50
Reply from 70.85.9.178: bytes=32 time=38ms TTL=50
Reply from 70.85.9.178: bytes=32 time=39ms TTL=50
Pretty close from here...