General questions about VestaCP
3 posts • Page 1 of 1
It is certainly a bug, In debian the use of cpu and ram is always the same. Centos does not have this problem.
This bug is in vestacp because accessing the server through ssh and using top -c displays the correct consumption.
The vesta team should correct this.