Quote:
if i get it clear, when a process grows up very much, then the swap memory will be used... when this process is done, the new processes of this program will keep launching on swap memory, because filesystem will be launched on real memory? why??
No. At one point that big process forced some memory into swap, when it completed or died most of the swap came back out, except for that 2% which nobody's actually needed to use yet. That's my theory on where the 2% swap came from and why it's just sitting there.
Quote:
So, when this very big process ends, then the processes on swap memory will get back at real memory, right?
More or less.
Less as in, memory won't come out of swap until they try to use it. This prevents some waste since that memory would be unused anyway and I think accounts for your 2% swap.
Quote:
and if there is more free memory, it will be used by filesystem... am i correct?
That's normal unless configured otherwise, yes.
Quote:
eventhough, as i mentioned at the beginning, on 2 identical servers the first uses memory as 20% system, 30% processes and 50% filesystem and on second one 20% system, 75% processes and 5% filesystem, and 4% swap!
Something big is hanging around, which used to be even bigger, I think.
Quote:
How can i identify on second server, the processes using 75%?
Have you tried ps aux? Or as madeingermany suggested,
ps -e -o pid= -o rss= -o vsz= -o args= | sort -k2,2n ? What does it look like?