[2017] tastyspleen IP may be changing (new hosting)

[Admin]

Salutations!

We're evaluating moving tastyspleen to a different hosting company in Dallas. (The current company is overpriced. I could save approx $300/month at the new place.)

The new hardware will be better in every respect (faster CPU, more cores, more RAM, SSD instead of HDD, faster network port.)

The question is: How are pings?

This page will show pings from various locations around the world: https://asm.ca.com/en/ping.php

To see pings to our current host, just use "tastyspleen.net". To see pings to what the new datacenter would be, use "testing.tastyspleen.net".

Note, however, this site doesn't always tell the whole story. My own ping to the new datacenter is quite bad. This appears to be the fault of my local provider (Time Warner) peering with telia.net and taking a really inefficient route. By contrast, a friend who lives a few miles away from me (Cox Cable instead of Time Warner) has a great ping to the new datacenter. So it can all depend on your local ISP.

So, if anyone who is interested could ping both "tastyspleen.net" and "testing.tastyspleen.net" and paste your results in this thread, it would be helpful to see how the new location would perform for you. [To clarify, in this case I mean running pings on your local computer, e.g. from a cmd.exe window or shell, not using the website mentioned above.]

Thanks,

quadz

[Admin]

280 

Compared to?

[Admin]

205

Not that there's anything I can likely do, but it'd be interesting to see the comparative traceroutes, to see the different routes your packets are taking in the two cases.

[quadz]

Top one is current, bottom one is new server


http://pastebin.com/zP3exNLm

Thanks. Not a fan of "telia.net". My Time Warner IP is also taking a route through "telia.net" to the new datacenter, and it's adding about 30 ms. (My ping to tastyspleen should be about 40. With the new route it's over 70.)

[quadz]

I have noticed over the last probably 6 months or more on the current server, there have been intermittent  lags where the whole server just stops (phone jacks) for like a second or 2 then goes on as normal. I am not the only player to experience this.

That sort of lag, in particular, I expect to be fixed by the new hardware. I get it too. The current hardware is old and slow, and the servers lag when they write to their logfiles. The new hardware would be both faster, have more RAM, and also have SSD-based storage, so I'd expect almost no such lag incidents.

I noticed in the first trace on the current server I am getting major packet loss through here

ae0.cbs02.cs01.lax01.networklayer.com -    3 |   38 |   37 |    0 |  187 |  197 |  188 |
|   ae7.cbs01.cs01.lax01.networklayer.com -   25 |   20 |   15 |  215 |  217 |  225 |  217 |
|   ae0.cbs01.eq01.dal03.networklayer.com -   80 |   10 |    2 |    0 |  214 |  215 |  215

Those are red herrings. All that matters is packetloss on the final hop. (Busy routers often drop traceroute packets (i.e. packets whose TTL has expired.)) In short: ignore any packetloss in the middle of the route, unless it's also reflected in the final hop.


-quadz

[yahoo]

205

Reply from 67.228.69.114: bytes=32 time=197ms TTL=50
Reply from 67.228.69.114: bytes=32 time=196ms TTL=50
Reply from 67.228.69.114: bytes=32 time=197ms TTL=50
Reply from 67.228.69.114: bytes=32 time=197ms TTL=50

[2d]

San francisco bay area........

[quadz]

Reply from 67.228.69.114: bytes=32 time=197ms TTL=50

Thanks, that's the current tastyspleen IP.

How does that compare to testing.tastyspleen.net?

[yahoo]

Pinging testing.tastyspleen.net [192.211.63.245] with 32 bytes of data:
Reply from 192.211.63.245: bytes=32 time=241ms TTL=49
Reply from 192.211.63.245: bytes=32 time=241ms TTL=49
Reply from 192.211.63.245: bytes=32 time=241ms TTL=49
Reply from 192.211.63.245: bytes=32 time=241ms TTL=49

Ping statistics for 192.211.63.245:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

[Whirlingdervish]

I'm seeing 38ms on "testing.tastyspleen.net" and about 35ms on "tastyspleen.net.

I wouldn't even notice that ingame.

[ImperiusDamian]

Getting about 51/52 ms to tastyspleen.net and 57/58ms to testing.tastyspleen.net. In North Carolina using Centurylink.

[Zeppelin]

tastyspleen.net:   143.408   143.577   144.010 (my ping in game is always around 130)   
testing:                 144.635   144.952   145.544


on cmd prompt:
ACTUAL:
A enviar para tastyspleen.net [67.228.69.114] com 32 bytes de dados:
Resposta de 67.228.69.114: bytes=32 tempo=129ms TTL=53
Resposta de 67.228.69.114: bytes=32 tempo=128ms TTL=53
Resposta de 67.228.69.114: bytes=32 tempo=128ms TTL=53
Resposta de 67.228.69.114: bytes=32 tempo=128ms TTL=53

TEST SERVER:
A enviar para testing.tastyspleen.net [192.211.63.245] com 32 bytes de dados:
Resposta de 192.211.63.245: bytes=32 tempo=131ms TTL=43
Resposta de 192.211.63.245: bytes=32 tempo=129ms TTL=43
Resposta de 192.211.63.245: bytes=32 tempo=129ms TTL=43
Resposta de 192.211.63.245: bytes=32 tempo=129ms TTL=43

[Sgt. Dick]

Current Tasty - 42

New Tasty - 48

[2d]

rofl dicklick will get owned 

[Sgt. Dick]

With my added ping, you might get a frag against me