new datacenter ping test

[Laurelin]

tastyspleen.net averages 110ms
new ip averages 102ms

(from Alberta, Can)

Either way - it doesn't matter to me. I mostly play on t4 or dfs.

[[BTF]Sigma]

Code: [Select]

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Mark>ping tastyspleen.net

Pinging tastyspleen.net [74.54.186.226] with 32 bytes of data:
Reply from 74.54.186.226: bytes=32 time=82ms TTL=55
Reply from 74.54.186.226: bytes=32 time=83ms TTL=55
Reply from 74.54.186.226: bytes=32 time=82ms TTL=55
Reply from 74.54.186.226: bytes=32 time=82ms TTL=55

Ping statistics for 74.54.186.226:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 82ms, Maximum = 83ms, Average = 82ms

Code: [Select]

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Mark>ping 66.228.118.51

Pinging 66.228.118.51 with 32 bytes of data:
Reply from 66.228.118.51: bytes=32 time=73ms TTL=244
Reply from 66.228.118.51: bytes=32 time=73ms TTL=244
Reply from 66.228.118.51: bytes=32 time=73ms TTL=244
Reply from 66.228.118.51: bytes=32 time=74ms TTL=244

Ping statistics for 66.228.118.51:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 73ms, Maximum = 74ms, Average = 73ms

C:\Users\Mark>
Good here

[BIG DICK RICK]

not that I count since I'm leeching wireless...but it looks pretty funny..

[[BTF]Defiant!]

ping averages is 15-20 ms slower than current tastyspleen.net

but do what must be done

[VaeVictis]

some people are getting a small increase... but some people are getting a huge decrease

whats wrong with the current ts server? getting full or too stressed?

[UUD-40]

Tastyspleen.net: 47ms average
softlayer.net: 43ms average

From San Diego, CA

[console]

UPDATE: There's a Q2 server now running on 67.228.53.218:27910 for ping testing - please try it out.


Thanks!

quadz

[yahoo]

doesnt connect for me

[console]

doesnt connect for me

Sorry, I typo'd the port number   

[VaeVictis]

hm... getting on the q2 server my pings looked about normal for a texas server, 60-65 like i get now... not the 75-80 that i got pinging the ip earlier

just pinged it again... still gettin like high 70s and up pinging it... it does seem a lot more spikey than tastyspleen's current server with spikes up over 90 or 100 every few packets

wonder whats up with in game pinging more than 10ms better...

[console]

whats wrong with the current ts server? getting full or too stressed?

Well, basically, I can save money, and end up with better hardware.

The current server has enough CPU, but it's running low on disk space.  And it's essentially a dead end legacy system now that ThePlanet was acquired by Softlayer.  There are several advantages to Softlayer servers that aren't available for my old legacy servers.

So I'm really hoping it works out...

[console]

hm... getting on the q2 server my pings looked about normal for a texas server, 60-65 like i get now... not the 75-80 that i got pinging the ip earlier

just pinged it again... still gettin like high 70s and up pinging it... it does seem a lot more spikey than tastyspleen's current server with spikes up over 90 or 100 every few packets

Does the spikiness show in your netgraph, or only from the command line pings?

wonder whats up with in game pinging more than 10ms better...

Well, routers often treat pings as very low priority packets.

Whereas the in-game packets should not tend to suffer from being treated as low-priority...

[l0ckp1ck]

mr quadz i tried the new server and i must say woohoo! 200 - 207 ping which is pretty good for me. Even if my ping went up to say 240 i would still say change it, cause at the end of the day u r the one who has to pay the bills so if it makes it cheaper for you, i don't think i would be too upset if i happened to ping say 240 -270 atleast i could still play.

[adz1La]

no difference for me.... 

[VaeVictis]

hm... getting on the q2 server my pings looked about normal for a texas server, 60-65 like i get now... not the 75-80 that i got pinging the ip earlier

just pinged it again... still gettin like high 70s and up pinging it... it does seem a lot more spikey than tastyspleen's current server with spikes up over 90 or 100 every few packets

Does the spikiness show in your netgraph, or only from the command line pings?

wonder whats up with in game pinging more than 10ms better...

Well, routers often treat pings as very low priority packets.

Whereas the in-game packets should not tend to suffer from being treated as low-priority...

spikes show on the netgraph, kinda like how tourney3 never had a completely smooth netgraph, always had small bumps.. i mean i guess its not TOO much of a problem, its not all that important in tdm and i dont like playing ffa in the first place all else fails ill spend more time on dfca lol

just a little confused on how in game i get 10-15ms less than pinging the server... cause even if ping packets are relatively low priority, 10-15ms is quite a bit