From: Rob Love <rml@tech9.net>
To: Mickael Bailly <mickael.bailly@telintrans.fr>
Cc: linux-mm@kvack.org
Subject: Re: looking for explanations on linux memory management
Date: Wed, 26 Nov 2003 13:13:29 -0500 [thread overview]
Message-ID: <1069870409.10070.8.camel@localhost> (raw)
In-Reply-To: <200311261830.02711.mickael.bailly@telintrans.fr>
On Wed, 2003-11-26 at 12:30, Mickael Bailly wrote:
> 1/ can you explain me what happened in week 47 so cached memory don't get down
> anymore ? Nothing really changed in this week on the server.
Somehow you started generating more page I/O and thus more page cache.
What actually strikes me as odd is the fact it was so low despite having
free memory.
But it could be a low vs. high memory thing, since you have 2GB of RAM.
The full output from /proc/meminfo and /proc/slabinfo might be more
useful than this graph.
> 2/ how can I know when my server needs more RAM/SWAP, if free memory is always
> about 0
When swap is abnormally large (or, even better, when swapped activity is
high. See vmstat(8)). Free memory being zero does not say much...
Linux will use most of available memory for cache, but will of course
prune that in response to page allocation.
> 3/ can you tell me where to find PER PROCESS memory usage (/proc/[process
> id]/stat ? /proc/[process id]/statm ? )
/proc/pid/status has VmSize, etc.
You can also see this with ps(1) and top(1), of course.
Rob Love
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-11-26 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 17:30 Mickael Bailly
2003-11-26 18:13 ` Rob Love [this message]
2003-11-26 19:01 ` Mark Hahn
2003-11-27 14:53 ` Mickael Bailly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1069870409.10070.8.camel@localhost \
--to=rml@tech9.net \
--cc=linux-mm@kvack.org \
--cc=mickael.bailly@telintrans.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox