Optimize SolusVM VPS Server
For the most part, the default CPU setting used by SolusVM will be enough for the average container (VPS Server). Some VPS servers might need to be optimized to get the best performance. But this is especially true if you have a cPanel server with a lot of websites on it but is also true for resource-hungry applications.
Remember, there is only so much optimization you can do, so you should take other factors into account like the type of CPU being used by the host node, and the storage type. But if you have a container that is deployed using SATA storage remember that this is the slowest type of storage possible and you will only get limited benefits from optimizing the container.
For the purpose of this article, we are going to use an E3-1270v6 hostnode running NVMe storage. The container will be deployed with 4 vCores, 4GB Ram and 10GBs of space. The OS will be CentOS 7. But for the test, we are going to run the standard Bench test used by most people. You can start the test by issuing the below command.
wget -qO- bench.sh | bash
Standard Test Results Running The Default SolusVM CPU Settings
So, unoptimized our VPS server returned the following results from the Bench test. But remember, this is an NVMe VPS , the results wll be higher than an SSD or SATA server.
CPU model : Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz Number of cores : 4 CPU frequency : 3792.012 MHz Ttal size of Disk : 10.0 GB (0.8 GB Used) Total amount of Mem : 4056 MB (14 MB Used) Ttal amount of Swap : 0 MB (0 MB Used) System uptime : 0 days, 0 hour 1 min Load average : 0.23, 0.09, 0.03 OS : CentOS 7.6.1810 Arch : x86_64 (64 Bit) Kernel : 2.6.32-042stab126.1 speed(1st run) : 433 MB/s I/O speed(2nd run) : 409 MB/s I/O speed(3rd run) : 503 MB/s Average I/O speed : 448.3 MB/s
Optimize SolusVM VPS
Now we are going to modify the CPU settings of the container to provide some optimization with the aim of improving the results we just got on the Bench test above. The most important value we are looking at in this bench test is the I/O speed, the time it takes this server to write to the disk and read information. As this is an NVMe VPS we don’t expect the results to improve drastically.
CPU Units – This is how much CPU time the container will receive if all the CPU power is used on the host node
CPU % – The CPU usage limit of the container. If the container has 4 vCores then the % would be 400% as default
I/O Priority – The priority of requests from this container. The lower the number the higher the priority.
For our container and this test, we increased the values of CPU units to 250000, The CPU % to 3400 and the I/O Priority to 2. So from the results, we can see the average I/O speed has increased by about 80 MBPS
CPU model Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz Number of cores : 4 CPU frequency : 3792.012 MHz Ttal size of Disk : 10.0 GB (0.7 GB Used) Total amount of Mem : 4056 MB (15 MB Used) Total amount of Swap : 0 MB (0 MB Used) System uptime : 0 days, 0 hour 10 min Load average : 0.00, 0.00, 0.00 OS : CentOS 7.6.1810 Arch : x86_64 (64 Bit) Kernel : 2.6.32-042stab126.1 speed(1st run) : 578 MB/s I/O speed(2nd run) : 555 MB/s I/O speed(3rd run) : 452 MB/s Average I/O speed : 528.3 MB/s
You can gain a better optimized VPS Server by modifying the default CPU settings inside SolusVM even when using a fast storage type like NVMe storage, If you optimize a server running SATA storage then the benefits will be clearly seen but to get real benefits you should consider changing any SATA servers to at least SSD storage and if possible NVMe storage for the best possible benefits.
How was this article? Optimize a SolusVM VPS Server Running Virtuzzo / OpenVZ
More from SolusVM
If you reinstall your VPS server and your using a KVM solution plus you have additional IPs attached to your …