Can an expert explain THIS kind of lag for me?

[ZERO]

Oh on this page you can see the current system wide network latency from your origin point. http://lg.softlayer.com/#

For example from this we know that the lag from Amsterdam to our server is <80ms plus the latency for the client to get to the Amsterdam datacenter.

So I know that I ping our servers in 24-30ms from my house. The atl datacenter pings in 15ms therefore the speed of my local network and internet to reach Atlanta takes about the same amount of time as my data does to go from ATL to the server in DC.

[Passarelli]

Cyber, you do know the parts of netgraph, right? The very large bars don't matter much. That is simply the amount of data coming into your computer from the server. It is the size of the packets you are getting. The very very bottom bar is what you have to watch. In several of your screenshots it looks as if you were recently extrapolating. You can tell this because the orange lines rise above the white border of the blue box. When this happens, your client is guessing for that period of time and thus will make things look choppy and people (or you) will jump around. You can adjust this by increasing your lerp settings. Ideally, you want your lerp just barely high enough so you never extrapolate. This will allow you the best responsiveness without people jumping around.

That said, it looks very very spiky on the screen shots. If it isn't something that happens when you are currently in a battle, I'd have to say its a network issue of some kind. Either your computer is initiating a new network connection and it eats all the bandwidth for a second or so (common of viruses) or there is something else going on. It could be either your NIC, router, modem, IP, or any IP between you and the server. You should pray it is one of the first 3 (or a virus) as these are all easily fixable. A tracert likely will not help you with this, as the issue looks to be very intermittent. You may want to first simply run a ping to your ISP while you play on a day where it seems very bad in terms of extrapolating. Do this by first running a tracert, and your ISP should be the second on this list (after your modem's IP). Then simply use ping -t IPaddress in the command prompt. As soon as you lag, stop it and look to see if you had dropped packets. If so, it is highly likely it is on your end (NIC, router, modem). If not, you will need a more advanced program as windows doesn't have the software available to trouble shoot this. www.pingplotter.com has a lightweight piece of software that you can run as you game. It will constantly run tracert to the specified IP (use the server). As soon as you lag, tab out and stop it and find where the packet is dropped. You'll want to do this a few times to make sure it is consistent, and then contact your ISP. If the hop is far away, it is likely they can't do anything about it other then notify whatever ISP is dropping the packets. The only other way around it would be to route your traffic around this hop.

Hope this helps!


EDIT: https://developer.valvesoftware.com/..._Network_Graph for an explanation of netgraph3. I know it says TF2, but they are the same!

[toma]

you have malware from all the cambodian midget goat porn.

Run Ping to 127.0.0.1 - tests ip stack
run ping to the gateway/router/switch - usually your router's ip address
run ping to your ISP
run ping to the hop before it hits the US side
run ping to server - tests connectivity...well to the server


watch the pings see where it fluctuates/drops if it does at all
if it also spikes when you ping 127...1 reinstall the drivers for the NIC as the stack is going bad
if it spikes at your gateway/router/switch try replacing the router or switch/try a different port if you have one available
if it spikes on the way to the server, contact your isp to see if they know of any outages along the way or issues

also another thing to do is run tracert to the server to see if the routes change when you notices spikes (hopefully the routing protocols the ISPs use are dynamic and will failover and shit), would signal network issues along the route.

that's for the network side.

Edit:
if you have a benchmark tool run it multiple times like 10 times in a row to see if there are any significant changes in the score, and do a comparison of other systems with similar build to see if you're losing anything to performance of hardware.