Are your cpu so bad or its just normal for srcds that it using fully 4 cores(80-100% cpu) to manage playable 128 tr(with pretty medium var values). On 2 cores the var value was pretty high(most of time red). Is it overselling or just beacause srcds dont like VM environment ? Anyone had such a problem ? I talking here about 10 players and clear server without any plugins mods(just matchmaking). Maybe amsterdam will be better next time ?
@Juri - It's important to keep in mind that, IIRC, the cores are not dedicated, they are shared, which means that you're given a "fair-share" allocation of CPU resources from X Cores where X is the # of cores assigned to the Droplet you deploy. This means that you may be able to use more CPU on a rather empty or newly deployed node (read: the bare-metal server that droplets are deployed on), whereas on a fuller node, you may not.
When it comes to gaming servers, IIRC, the GPU also comes in to play and alleviates much of the CPU load that would normally result by offloading the processing to the GPU. Since DigitalOcean primarily caters to developers, I would say that the nodes are not setup with more advanced GPU's that would ultimately be the most suitable for gaming, whether it's a limited slot server or one that hosts far more.
It finally runned without a problem - but i had use.... 8 cores droplet. It's using them pretty heavly like 60-80%, but im using it like max 5 hours a week. Can i get banned for something like that ?
@Juri - To expand on the CPU's, looking at one of my current Droplets deployed in New York 3, I'm seeing Intel E5-2630L's, which are 2.4GHz Hex-Core CPU's (12 Cores w/HT) with a 15MB Smart-Cache. While they are not the newest in terms of being the latest releases from Intel, they are pretty nice CPU's.
That said, server loads are the result of more than just CPU usage. It's what causes the CPU usage and what surrounds it (i.e. high Disk I/O for extended periods will result in high CPU usage and as a result, high CPU load -- the same for OOM, or Out of Memory).
You can run the following command, as
root:to see what CPU('s) are being ran on your Droplet.