From: Miquel Colom Piza <m.colom@barcelo.com>
To: linux-kernel@vger.kernel.org
Subject: Calculation of private memory of processes for estimation of RAM in big server
Date: Mon, 11 Jun 2001 12:30:50 +0200 [thread overview]
Message-ID: <3B249DDA.E9D69933@barcelo.com> (raw)
I would like to know how to calculate the amount of private memory (i.e.
memory used only by that process) so I can estimate the total amount of
RAM I have to put in a heavy loaded server.
In Sun Solaris I use a tool called pmap that gives me a resume of the
private and shared memory and the size image of each process. This pmap
utility uses the /proc filesystem to obtain the information.
In Linux I've used ps axl and I think that the RSS column is the right
one, but I'm not sure. Also I've look at the file
/proc/<PID_OF_PROCESS>/status that has, for example, these lines:
VmSize: 1144 kB
VmLck: 0 kB
VmRSS: 52 kB
VmData: 28 kB
VmStk: 8 kB
VmExe: 56 kB
VmLib: 1024 kB
But again I'm not sure which one of these numbers is the one to look at.
Could please
any VM guru help with this?
Please CC me because I'm not subscribed to the list
Best regards
Miquel Colom
reply other threads:[~2001-06-11 10:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B249DDA.E9D69933@barcelo.com \
--to=m.colom@barcelo.com \
--cc=linux-kernel@vger.kernel.org \
/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