Subject: hashify and memory saving
From: Tor Rune Skoglund <trs@swi.no>
Date: Fri, 1 Jan 2016 21:37:52 +0100
Fri, 1 Jan 2016 21:37:52 +0100
Hello List,

Having been a happy linux-vserver user for more than 10 years now, it 
was about time to test the hashify feature. The disk savings are 
obvious, and easily measured, but I have been trying a lot harder to 
measure any possible run-time memory savings. For the testing, I created 
a simple template LAMP guest, and a lot of hashified guests cloned from 
that one. I am unable to measure noticeably less memory usage when 
running multiple hashified guests compared to non-hashified ones using 
free and /proc/meminfo/'s MemAvailable entry.

However, this could very well be to shortcomings in my own understanding 
how this should work or what to look for.

What should I look for regarding possible memory savings? Anyone with 
any pointers?

This is Gentoo, util-vserver 0.30.216_pre3120, kernel Linux amd64 
3.18.7-vs2.3.7.4.

BR, Tor Rune Skoglund
trs@swi.no



Hello List,

Having been a happy linux-vserver user for more than 10 years now, it was about time to test the hashify feature. The disk savings are obvious, and easily measured, but I have been trying a lot harder to measure any possible run-time memory savings. For the testing, I created a simple template LAMP guest, and a lot of hashified guests cloned from that one. I am unable to measure noticeably less memory usage when running multiple hashified guests compared to non-hashified ones using free and /proc/meminfo/'s MemAvailable entry.

However, this could very well be to shortcomings in my own understanding how this should work or what to look for.

What should I look for regarding possible memory savings? Anyone with any pointers?

This is Gentoo, util-vserver 0.30.216_pre3120, kernel Linux amd64 3.18.7-vs2.3.7.4.

BR, Tor Rune Skoglund
trs@swi.no