Best way to improve latency

[Janus]

Since I started mboxing, my latency is higher than what it has been. It's usually in the 150-250 ms range.
I have roadrunner turbo at 20 MBps (the highest speed/service available in my area)

Question is what can I do to improve the latency of my games?
Any ideas?

[Tim]

ping 8.8.8.8 -t 10


What is it showing you? Paste a screenshot.

Then do a:

tracert 8.8.8.8

Paste a screenshot of that

That would give us a good first round of what to go by

[Drarkan]

I've been having the same issues actually. I'll have to try that too when I get home. I've been getting pings of 250ms to up to 500 or more in some cases.

[Janus]

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms TIMECAPSULE [10.0.1.1]
2 * * * Request timed out.
3 10 ms 7 ms 5 ms network-065-026-189-141.indy.rr.com [65.26.189.1
41]
4 20 ms 8 ms 10 ms network-065-026-189-138.indy.rr.com [65.26.189.1
38]
5 32 ms 23 ms 22 ms network-065-026-189-061.indy.rr.com [65.26.189.6
1]
6 58 ms 38 ms 34 ms son0-1-0.clevoh1-rtr0.mwrtn.rr.com [65.25.137.18
5]
7 34 ms 35 ms 35 ms ae-3-0.cr0.dca20.tbone.rr.com [66.109.6.70]
8 42 ms 32 ms 39 ms ae-1-0.pr0.dca10.tbone.rr.com [66.109.6.165]
9 29 ms 34 ms 30 ms 74.125.49.181
10 31 ms 36 ms 31 ms 216.239.48.108
11 33 ms 30 ms 33 ms 64.233.175.109
12 39 ms 47 ms 51 ms 216.239.49.149
13 34 ms 33 ms 33 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

[Janus]

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=32ms TTL=53
Reply from 8.8.8.8: bytes=32 time=36ms TTL=53
Reply from 8.8.8.8: bytes=32 time=37ms TTL=53
Reply from 8.8.8.8: bytes=32 time=33ms TTL=53

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

[xartin]

one thing i could contribute here with my background in cisco network engineering which i'm sure tim could offer some contributing information about that you might consider is that all routers and switches have a peak ability by design to process whats known as packets per second.

A not as often known fact that even if your switch or router is utilizing it's peak data transfer rate in each interface it still may have an adequate packet per second processing reserves. Running multiple applications which require network communications on one network gateway can exponentially increase the resource requirement demands on networking hardware from having to process millions of data packets

The reverse applies as well... often cheap retail grade routers and switches will exhibit poor network performance from high packet per second processing demands and this can cause very irritating latency that can be difficult for anyone to diagnose.

[Tim]

True everything has limiting factors including PPS, but even the super low end linksys device can handle ~800 entries in its translation table and around 40k PPS. I've benchmarked the crapload out of them. You can even do a hack to up the xlates to the 4000s, but in all reality, its a crapload.

Probably just an ISP issue really, cable companies are notorious for overselling.