hellreturn

Either only your DB files and server.dat file inside your silent mod folder or your full server files so that I can just start the server (Remove u rcon) This way i can recreate replica of your server on my machine and see if it lags or not. If it lags on my machine also then we can investigate more and if it doesn't then it's your machine/server issue.

That one is showing more usage because probably it's a node issue where your VPS is hosted. Probably overselling OpenVZ. I could be also wrong.

To be honest benchmark will not help you much unless you have your own dedicated server. If you have your own server I would suggest using munin or any other lower level monitoring tools to monitor your HD, CPU and RAM usage. Munin has good plugins too.

Those values seems fine for SATA 3Gbs devices or VPS/VDS. I had same issue on one of my windows server and it got auto resolved when I added new hard drives to my server. Since you guys have linux try ioping also. It would tell you latency of hard drives at the time of map start. Let's try this: 1. Install ioping. 2. Run ioping and monitor it during map start. 3. See if you see any increase in latency causing CPU halts. 4. Remove the DB and then start the server again. 5. If no red spikes and no increase in latency spikes of hard drive after removing DB files then it could be HD I/O issue. For debian just do apt-get install ioping Example: 4096 bytes from / (simfs /vz/private/3581): request=1 time=0.1 ms 4096 bytes from / (simfs /vz/private/3581): request=2 time=0.1 ms 4096 bytes from / (simfs /vz/private/3581): request=3 time=0.4 ms 4096 bytes from / (simfs /vz/private/3581): request=4 time=0.4 ms 4096 bytes from / (simfs /vz/private/3581): request=5 time=0.3 ms 4096 bytes from / (simfs /vz/private/3581): request=6 time=0.1 ms 4096 bytes from / (simfs /vz/private/3581): request=7 time=10.8 ms 4096 bytes from / (simfs /vz/private/3581): request=8 time=6.0 ms 4096 bytes from / (simfs /vz/private/3581): request=9 time=0.3 ms 4096 bytes from / (simfs /vz/private/3581): request=10 time=1.6 ms 4096 bytes from / (simfs /vz/private/3581): request=11 time=0.2 ms --- / (simfs /vz/private/3581) ioping statistics --- 11 requests completed in 10530.4 ms, 547 iops, 2.1 mb/s min/avg/max/mdev = 0.1/1.8/10.8/3.3 ms During any map start game read all pk3's.. so if that time HD I/O increases then server can handle, then it could give red spikes to players.. Once map is loaded it would be all fine... That was the case with me cos my server hard drive got old. Diabolic / mp_no can I host your server files for testing purpose and see if you are getting same red spikes or not? Just to make sure it's not environment issue? PS I also use munin for monitoring server usage... if any of you are interested here is the link: http://munin-monitoring.org/

If that fixed the issue then it seems like HD I/O issue on your server. Try this command on u Linux shell and dd if=/dev/zero of=test bs=64k count=16k conv=fdatasyncAnd post the output here. It might give an idea if something is wrong with hard drives.

I believe somewhere I had read that they are going to change it... Not sure where I read it.. but it was in news couple of weeks back.