On Thu, 2003-08-28 at 21:15, Jason Williams wrote: > What caught my attention was that the Mem: field -> used goes up about 8k > every couple of seconds...and im not sure why... > > Is there anything I can do to figure out what this is? make sure it is not > a problem and if it is a problem, correct it? > If you need more output, let me know... >
I remember having this kind of question on SunOS. I've been told by Sun's guru (not actually from Sun) that when a process terminates, it stays in memory as long as the memory is not requested by another process. So even tough I killed all my user processes, the memory usage was still loaded. The reason why the process remains in memory is because it speed up the processing when a process is often loaded and unload. The load times after the first load are faster since the whole application code is already in memory. I don't think Linux uses this way in it process management but I'm not sure. Another hint might be some device drivers, especially file systems, that may cache disk information in memory. If a process is really leaking memory, you should be able to see in TOP. When TOP is loaded, type 'M' to sort the process by memory usage. This could lead you to the 'RAM hungry one... As the saying goes: free memory is bad memory... Regards, Yanick Poirier. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
