Is SE Going to Fix Server Lag?

[Raist]

Just curious if any of you guys have tested you latency to your servers.

I'm consistently sitting at no worse than 80-90 ms response times, peak times on weekends it can sometimes hit around 110... but it's consistently very low for me. It's still often pegging no worse than around 230-280 or so to the JP servers, but the ones to Canada are consistenly low.

This can be a MAJOR factor in contributing to your lag.... and SE may have little to no control over latency across the internet.

Just saying, SE may be very limited in what they can do for people in some regions or with some ISP's.

[Edit:]
Just to provide an example, here are some quick ping results, taken at about 11:40 AM on a Sunday, Eastern time:

Midgard server:

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

One of the JP servers I stay connected to when online (also in the subnet used for XI, mind you):

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

If you run tracerts, you may see that the response times sometimes swing really high at one of the hops in between--SE has no control over that. Someone would need to go to the admins for that segment to address issues with their systems... not really SE's responsibility, maybe not even your ISP (unless it's their segment or one of their affiliates I guess).

Your best bet may be to find such hiccups in routing and forward it to your ISP. I did this once a few years back when having stability issues with XI, only to find it was a segment in Virginia that was failing, and RR was able to come up with a workaround for it. It happened again later that year and it was in Nova Scotia--BOTH times it was a problem with a VERIZON segment we were hopping on---and both times RR was able to provide a solution to the problem---NOT SE.