🚀 go-pugleaf

"Ron Gibson" <rsgibson@verizon.net> wrote in message
news:pan.2007.05.22.21.33.30.59332@verizon.net...
| On Tue, 22 May 2007 22:26:33 +0100, Andrew wrote:
|
| >>So I got to wondering what would be acceptable as the slowest line
speed.
|
| > As a client, probably 128k, maybe 256k. Ping, lag and packet loss
are far
| > more important than raw download speed.
|
| Oh boy. Thanx for the quick answer. I am familar witrh those terms
but
| have not ever measured lag or packet loss.
|
| Guess I got a new project now, huh :-)
|
| ...I DID read "Networking for Dummies" !
|

Hey Ron, I forgot  you mentioned your UT addiction.

Get pingplotter, a great tool for diagnosing network latency.
www.pingplotter.com

And yes, I'm a UT addict also, tho my playing time has slowly faded
due to undesirable network latency experienced on both of my broadband
connections (comcast and ATT DSL).

It's not the connection speed that matters as much as the routing to
the game server.  Also, asymmetric routing is a source of weird or
undesirable gaming response.  I finally resigned myself to the fact
that being routed through Chicago was simply going to be a PITA until
major network improvements were made.  I experience a lot of ping
spikes during online gaming, even when playing on Chicagoland game
servers.  Much of this is attributable to Level3 and Cogent networks
(and other "2nd tier" providers) who use odd routing algorithms that
create "alternating routes" to the game servers.  IOW, my data does
not flow to the server over the same route, and when this alternating
routing occurs, the games don't seem to like the small  yet
identifiable differences in latency.  Cogent network routing is almost
a guarantee of considerable spiking during the evening hours.
-- 
Best regards,
Kyle