skyride Wrote:Ping and bandwidth have absolutely ZERO correlation between each other.
no. if your data rate comes close to the bandwidth, the ping will rise. this might already happen very early. during my nightly backup to my ISPs ftp server the connection is load at ca. 50% (because I limited the upload) and the ping rises by 80ms or so.
but of course, this does not mean your ping is good if you have a high bandwidth (that's what skyride probably meant).
Oen386 Wrote:I did top, and it says 95+%. I assumed that high CPU usage was related to a lack of RAM.
this might be the cause of the problem. if your ram were limited your system would swap. afaik this would not lead to a high cpu load (maybe high IOWAIT% or perhaps high SYS% but not USER%). either your cpu (you still did not answer what cpu it is, the GHz has no meaning anymore, Xeon is a product line, not a cpu family) is too slow to handle whatever you are doing at your server (bots?), or you have some nasty system settings leading to a high cpu load.
I always say that I would not look at the cpu load, because it does not mean much. But if you are running at 100% and having lags this might nevertheless be a hint to the problem ;-)
btw: yesterday I upgraded my root to 2.6.29-rc4-rt2. now I have seen that srcds has taken more than 100% cpu load some times (up to 200% for a very short time - more is impossible as I have only 2 cores). maybe the assumption that srcds supports only one cpu is incorrect? maybe it only requires a very recent kernel? I am not sure, but unfortunately the interrupt load has rised also with the uprade...
EDIT: That is probably an artefact of top. htop and some other tools do not show this high cpu load. really strange, but it might be due to the fact, that 2.6.29 is still a RC not a release...