Hi,
I'm coming back on this, as servers with more and more ram appears,
the free command show very false values.
With 32Gb of ram, just after reboot I have 280MB of ram used (on -/+
buffer/cache line :used)
just after the end of "updatedb", I can see more than 3GB of ram used
(YES 3GB of RAM on
Hi,
Ok, so I did the work myself for those who are interested :
before :
total used free shared buffers cached
Mem: 33088172 9587560 23500612 0 921836 6832320
-/+ buffers/cache: 1833404 31254768
Swap: 33554424 0 33
tags 565518 upstream
thankyou
On Sun, Jan 17, 2010 at 11:28:19PM +0100, Nico wrote:
> slab cache usage (after the find/updatedb with a scan of all the
> filesystem). This kind of memory usage
> does not reflect user point of view,
> because as soon as a program request memory, slab cache is reduced
Hi,
2010/1/17 Craig Small :
> On Sat, Jan 16, 2010 at 04:41:35PM +0100, Nicolas Parpandet wrote:
>> The "free" cmd does not show properly used memory, as you can see,
>> slab is not taken into account, "used / buffer cache" is a useless
>> information,
> Hello,
>
> It's a big call to say "not sho
On Sat, Jan 16, 2010 at 04:41:35PM +0100, Nicolas Parpandet wrote:
> The "free" cmd does not show properly used memory, as you can see,
> slab is not taken into account, "used / buffer cache" is a useless
> information,
Hello,
It's a big call to say "not show properly" with anything at all to do
Package: procps
Version: 1:3.2.7-11
Severity: normal
Hi,
The "free" cmd does not show properly used memory, as you can see,
slab is not taken into account, "used / buffer cache" is a useless information,
for instance on this server :
r...@vzb:/etc/apt# tail /dev/zero
Processus arrêté
r...@vzb:/
6 matches
Mail list logo
