On 11/18/2016 07:39 AM, Frédéric Bron wrote:
While tmpfs does utilize RAM it will actually move contents to swap in the event RAM is
actually needed.
So that's normal that my RAM looks full (in top) and the swap and /tmp
are empty. This means that I still have about 8Gb free RAM available,
right? I am happy then.
You have all 16GB available. That "8GB" for /tmp is just a limit. The
actual space used grows and shrinks as you add and delete files there.
Think of it like the ulimit for process size. Just because processes
might be allowed to grow to 4GB doesn't mean that all processes _use_ 4GB.
There really isn't a lot of difference between /tmp in RAM and /tmp on disk.
With /tmp on disk, files are written initially to the buffer cache, and
get flushed out to disk when something else needs the RAM or,
eventually, by the automatic push of dirty buffer pages. For the latter
case, a copy of the data remains in the buffer until something else
needs that RAM. Short-lived files might spend their entire lives in the
buffer and never get pushed out to disk.
With /tmp in RAM, files get written to the RAM pages and get pushed out
to swap when something else needs the RAM.
The only difference is whether longer-lived files always get written to
disk regardless of the memory load.
As for RAM appearing full, see <http://www.linuxatemyram.com/>.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
