Little lag spikes

[VaeVictis]

ive been spiking a bit lately and its really fucking up my aim :/ just tiny spikes, i look at my netgraph and usually its 100% smooth at the flat 60, solid green bar... but lately ive noticed a TON of little spikes, seem to be up to 80 and 100 about judging from how high they are...

also getting a lot more connection drops where i just freeze and get the "old frame" message... and i seem to have problems here and there where it feels like that just happened but it didnt, ya know those times when lag is catching up and you move really funky for a second because all the movement commands are catching back up? :/

its also acting a bit like packet loss, but i have no packet loss right now... wont fire some times, doesnt render the rail core others... really a pain

its really screwing me up... wondering if anyone else has been having this problem lately before i call up my isp and bitch...

[VaeVictis]

ok the lag command registered packet loss client -> server but my netgraph didnt show ANY packet loss... the only bad spots on my netgraph were from the connection drop/freeze :/

[VaeVictis]

gah, fuck this i cant play when my connection is freezing every few seconds

[reaper]

Try going to:
run>>msconfig

turn the services off you don't need, and make sure other unnecessary proccesses aren't running.  then on the programs that configure themselves to start on boot, turn those options off in them.  I'm not sure what PC issues would show in the netgraph, but they can most definately cause sluggish issues.  by the way, other people have the same problems you do, and regardless quit complaining

[[BTF] Reflex]

That looks like an update maybe,  not quite that big when java updates,  but close

[VaeVictis]

That looks like an update maybe,  not quite that big when java updates,  but close

eh... update wouldnt do it over and over and make me freeze ingame while doing it :/ owuld just shoot my ping through the roof... those huge shark fin spikes are full drops where i freeze

[reaper]

play a game locally to see if it's the PC, if it is - see above

[VaeVictis]

play a game locally to see if it's the PC, if it is - see above

havent updated ANYTHING since awhile before it started, so it shouldnt be anything on my end... its probably just comcast being terrible -.- once it gets cold, it turns to shit, once it gets hot, it turns to shit, if nothing is going on and it should be perfectly fine, it turns to shit.... thats just comcast

[reaper]

then why not run a simple test

[console]

I'd recommend lowering your cl_maxfps drastically for diagnostic purposes, like to 30 or so.  (can set cl_async 1 and keep your r_maxfps high so it should be tolerable except for possibly stymieing your jumps a bit.)

Awhile back, there was a period where my ISP started getting spikes like that when I sent a lot of packets/sec out the port.  Lowering cl_maxfps worked around the problem.  (Lasted a few months, as i recall.)

So, might be worth a try...

[VaeVictis]

I'd recommend lowering your cl_maxfps drastically for diagnostic purposes, like to 30 or so.  (can set cl_async 1 and keep your r_maxfps high so it should be tolerable except for possibly stymieing your jumps a bit.)

Awhile back, there was a period where my ISP started getting spikes like that when I sent a lot of packets/sec out the port.  Lowering cl_maxfps worked around the problem.  (Lasted a few months, as i recall.)

So, might be worth a try...

kewl thanks, ill give it a try

seems to only happen a lot during peak hours like noon :/ so it could be a heat problem with an exposed line maybe? or it could just be traffic at noon is a bitch and im sending too many packets so it spikes terribly like that

[reaper]

first "rule out" the PC.  and if it is the ISP, the cause is unknown, most likely it is congestion, datagrams wait in queues , that's why you could see no red, but get a higher line.  there's various types of queues at various levels, but the idea is basically/usually first in first out, practically nothing is setup for games.


you could also rule out the local line,  but it's easier to do that with the PC, and I put "rule out" in quotes because it's not a perfect test, but if your PC shows issues playing locally, time to look at the PC..