Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

interpreting top



It is normal for a Linux kernel to grow the cache and buffers infinitely to
consume all available ram, over time.  It will then opt to sometimes swap
out idle processes, or throw away cached files from memory, as processes
request more memory for active processing.

You don't get valuable information from the free/used.
But if you see the free staying very small ... and you see the cache &
buffers becoming very small ... then you don't have enough ram.  In your
case, it's quite the opposite.

I am guessing this server is either httpd, or a fileserver.  Active
processes consume almost no memory, processor almost totally idle, and the
kernel is using all the ram for caching.







BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org