On Mon, 2003-03-31 at 11:54, Soren Harward wrote:
> One of two things is happening -- and it's probably a combo of both.
> One, building a large database such as the slocate database just takes
> up quite a bit of memory. However, I doubt that updatedb itself is
> actually eating up all 300MB -- you can try running "ps aux | grep
> updatedb" while the process is running just to check how much RAM it is
> using. Most of the RAM being used is most likely disk cache. Since
> updatedb runs through almost the entire hard drive to look for the
> files, you'll end up with a lot cached.
>
> How much RAM do you have in this system?
I have 512 MB. This is what free reports under normal usage:
total used free shared buffers cached
Mem: 514360 359356 155004 0 24404 157160
-/+ buffers/cache: 177792 336568
Swap: 208804 0 208804
By normal usage, I have KDE 3.1, Evolution, Phoenix, a couple of
terminals, and Visual Slickedit running.
After running the cron job, The second line, (memory - used + buffers +
cached) is only 140000 - 160000, and that is often times with just KDE
and nothing else running. So, I don't think it's being cached.
Grant
____________________
BYU Unix Users Group
http://uug.byu.edu/
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
