nitz

Xenithar, you mentioned earlier in this thread you were using Athlons MPs, aren't these Athlons based on the Athlon XP architecture? If yes, they're running at 2.13 GHz (named 2800+ to compete with Pentium 4 2.8Ghz). While they're server CPUs, they're identical to the Athlon XP parts except for the dual CPU support which was an extremely efficient platform versus the Pentium 4 based Xeons at the time. You can't compare them to a Core 2 Duo, it's a completely new architecture which is much more efficient per clock. You can run down two Athlons MP running at 2.2Ghz (3200+) versus a Core i3 downclocked to 1.0Ghz and the Core i3 would still win any benchmark you throw at it. And at stock speed the new processor would be at least 5-15x faster. I have tested the CPU usage on my old laptop with a Core 2 Duo T6500 @ 2.10Ghz, same DB as my CentOS box with the latest mangos revision and the CPU is always at 0-2% with no players so having Mangos ALWAYS at 35% is a bit weird IMO.

That CPU is more than enough to run Mangos for a few players and a home server, do not underestimate the CPU speed. You could try CPU Limit, it's a small utility that let you set a max percentage of a process in Linux, you might find yourself setting a limit of 5% and still perform nicely for a couple of players. I would try a clean DB(with UBB) and see if the CPU usage is the same, I've had issues with some loop caused by something in my DB due a faulty sql update that caused high CPU load once. These are the stats of my server running mangos rock solid using screen with about 3-8 players getting online daily: System uptime 8 days, 2 hours, 35 minutes Running processes 85 CPU load averages 0.09 (1 min) 0.13 (5 mins) 0.10 (15 mins) CPU usage 0% user, 0% kernel, 0% IO, 100% idle Real memory 2 GB total, 1.01 GB used

Ok, it wasn't TBB or ACE that I had trouble with, actually I figured out the problem is much simpler! When using nohup it makes mangos eat 100% of CPU in background. Since I'm administering the server through SSH once I leave the session it kills all my processes so nohup is supposed to fix it by sending the process to background and it's output to a file however it makes mangos go crazy consuming all the CPU. I am not sure if it's a mangos or a nohup issue. Screen works much better for this so you can leave the SSH.

Apparently compiling mangos with external TBB and ACE was my issue. - Wrong, see my post below After recompiling mangos with both use external set to 0 here are the results: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1912 nitz 16 0 420m 250m 10m S 1.0 12.2 0:22.35 mangosd Basically it's using 1% CPU and 12.2% memory with 3 players online, that's amazing. I am in love with Mangos after trying a dozen of servers and a lot of headache, mangos just works and it's rock solid.

Hello guys, I'm playing around with my own server, it's modest, a VM with one Xeon 2.8Ghz *dedicated* core and 2GB ram on CentOS 5.7 64bits and 1000mbps shared uplink. It was troublesome to compile mangos, I had problems with TBB and ACE X CentOS plus many other stuff. Currently my server has vmaps enabled and about 43 characters, the MySQL database is hosted in the same machine, there are rarely over 5 players online but the CPU is ALWAYS at 100%. I was hosting this same server on a Windows machine with a Core 2 Duo 6750 with 2GB ram and Windows XP and the CPU use was pathetic. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 24633 nitz 15 0 324m 209m 10m S 98.7 17.3 659:10.84 mangosd The database is the same and it's fairly decent comparable to the Core 2 Duo box considering it's now entirely dedicated to the server. Server is working fine but this 100% cpu at all times worries me. Any thoughts? Thank you