@sleddog when your provider is overselling and the OpenVZ host node runs short of memory it will artificially increase the used memory, so for example a 1MB of real usage might show as 5MB in the guest if there is not enough memory on the node.
That's my local dev box. No over-selling, no over-allocation. The u14 container is running nginx, mysql, php with several php pools, plus other stuff. It's not happening in 6MB RAM.
Comments
A comparison of your running processes would be more helpful than a web min screenshot.
How much of the memory consumed on 2 is actually just cached?
What processes would be be best? I would rather not try and post them as I'm not sure how to do it other than an image.
No1
Memory mysql 742.20 MB /usr/sbin/mysqld
No2
Memory mysql 949.34 MB /usr/sbin/mysqld
downloadmoreram.com will assist you.
417.88 MB cached
And on one
839.24 MB cached
Could as simple as extreme overselling looking at your cores
How would overselling make your memory usage go up??
The difference is due to memory reporting quirks with recent OpenVz kernels.
The box with the 2.6.32-42stab108.1 kernel is under-reporting its memory usage. Actual memory usage is higher.
Try my ofree script on both boxes and compare:
https://github.com/sleddoggy/ofree
Read more...
http://kate-cms.com/memory-reporting-with-recent-openvz-kernels/
http://www.linuxatemyram.com/
Run 'sync; echo 3 > /proc/sys/vm/drop_caches' from ssh and then compare their memory usage. It's more accurate.
Here we go
Box1
ofree,
Mem: total 3072, used 1131, free 1941, shared 516, cached 619
-cache: used 512, free 2560
Swap:0, 0, 0,
free -m,
Mem: total 3072, used 1130, free 1941, shared 516, buffers 0, cached 1105
-/+ buffers/cache: used 25, free 3046
Swap: 0, 0, 0,
===========
Box2
ofree,
Mem: total 4096, used 674, free 3422, shared 70, cached 424
-cache: used 250, free 3846
Swap: total 4096, used 1, free 4095
free -m,
Mem: total 4096, used 670, free 3425, shared 69, buffers 0, cached 423
-/+ buffers/cache: used 247, free 3848
Swap: total 4096, used 1, free 4095
Thanks but as root all it returns is "Permission denied" on both machines.
So 'ofree' shows Box 1 is using 512MB RAM. That's reasonable seeing it has 5 WP sites and woocommerce.
On the box with the older kernel, free/ofree give pretty much the same result.
You can't do that in an OpenVZ container.
So is it all down to the age of the kernel!
I was going to keep the 3GB box but will let it go now by the looks of it.
I forgot to thank you for the script it cleared thing yo for me well done
@sleddog when your provider is overselling and the OpenVZ host node runs short of memory it will artificially increase the used memory, so for example a 1MB of real usage might show as 5MB in the guest if there is not enough memory on the node.
I think the issue is just cosmetic. Not a reason to cancel the box if you're happy with it and the provider
And in what circumstances does it artificially decrease the reported used memory (which is the issue here)?
Not work for OpenVZ.
i am 100% this issue is for overselling ! ask your provider to change your vps to another node , you will see the diference.
On which vps do you think the overselling is taking place 1 or 2 ?
And I'm 100% sure it isn't.
http://pastebin.com/rUcPVJuZ
That's my local dev box. No over-selling, no over-allocation. The u14 container is running nginx, mysql, php with several php pools, plus other stuff. It's not happening in 6MB RAM.