Forums › English Language Forums › Technical › Technical Issues

Buscar

Latency - the need to properly check and get results to have ISP correct problem

2 respuestas [Último envío]
Vie, 11/09/2012 - 23:44
Imagen de Dbugz
Dbugz

G'day.

Latency in online games is a huge factor for smooth and enjoyable gameplay.

My personal experience with running SK, coming from SEA region, is that a latency of approx < 270ms and jitter/variance of < 10ms (all as per pingtest.net) is still manageable and does not result into lagging into traps/shadow fire, ghosting through walls/impassable objects, delayed attack hits, rubber banding, etc. Also, it is imperative that the SK client be forced to connect only to US East as it is geographically closer in terms of submarine cables.

In the prior months, I've already been struggling to get a decent connection with my DSL provider and usually after a dozen re-cycling my connection would get me a "good" connection as stated above.

However, just recently my provider has made changes to their infrastructure (without informing us customers of course) and now every time I establish a connection and try running SK i just get all the terrible things associated with a very bad latency, or as we could say horrendous amounts of lag.

Running latency checks via pingtest.net now show latency ranging from > 400ms up to 1600+ms (and at times even higher), with jitter/variance ranging from > 190ms up to 800+ms.

I sincerely doubt my provider would help resolving this issue without me doing all the dirty work for them, such as getting latency results, traceroutes, and what have you.

If the developers of SK would be so kind enough as to point me to the right direction on how to be able to get proper latency and traceroute results that test directly against SK servers it would be most appreciated. I do understand that the community does checks via the popular pingtest.net site but I do believe that is insufficient as it does not test directly against the actual US East game servers of SK.

As for the community, has anyone been able to get such exact information as well and would be so kind enough to share it with the rest of us.

TIA.

Sáb, 11/10/2012 - 09:18
#1
Imagen de Dogrock
Dogrock
The reason we use the

The reason we use the PingTest service is because the Amazon EC2 hosting SK uses does not allow direct ping attempts. Traceroutes are similar, once it gets to the edge of the Amazon network the request starts timing out. The Asburn, VA test site is used since it's one of the physically closest locations to Amazon's data center.

Sáb, 11/10/2012 - 19:21
#2
Imagen de Dbugz
Dbugz
.

@Dogrock

Thanks. Yes, I do still use Pingtest for now given the circumstances.

Sitio elaborado con Drupal, un sistema de gestión de contenido de código abierto