What you are seeing is load being generated by other users on the same server node. In our environment we are using LXC linux containers rather than QEMU virtual machines to provide a secure multi-tenant platform.
There are many benefits to this approach including better network and disk performance, as well as drastically reduced overhead because your VPS does not need to run a kernel. This also means you get to see more details of the underlying server hardware, including physical CPU utilization where other users' utilization will appear as system utilization. Unfortunately HTOP does not distinguish between system CPU utilization and user utilization, so it will appear as your own.
There is no need to worry about loss of performance, as CPU cores are dynamically assigned - when you generate load your processes will be run on the least loaded cores available.
F
Fedon
said
about 1 year ago
Is this also the reason for the 'ps' command in my Ubuntu VPS displaying 0.0 percent process CPU usage even for processes using high CPU?
M
Matt
said
about 1 year ago
Correct, since containers are nested the CPU usage being reported is for the entire system as opposed to any one vps.
What you are seeing is load being generated by other users on the same server node. In our environment we are using LXC linux containers rather than QEMU virtual machines to provide a secure multi-tenant platform.
There are many benefits to this approach including better network and disk performance, as well as drastically reduced overhead because your VPS does not need to run a kernel. This also means you get to see more details of the underlying server hardware, including physical CPU utilization where other users' utilization will appear as system utilization. Unfortunately HTOP does not distinguish between system CPU utilization and user utilization, so it will appear as your own.
There is no need to worry about loss of performance, as CPU cores are dynamically assigned - when you generate load your processes will be run on the least loaded cores available.
Correct, since containers are nested the CPU usage being reported is for the entire system as opposed to any one vps.