From: Andrew Morton <akpm@digeo.com>
To: Cliff White <cliffw@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OSDL][BENCHMARK] OSDL-DBT-2 - 2.4 vs 2.5 4-way/8-way with vmstat
Date: Fri, 31 Jan 2003 14:57:35 -0800 [thread overview]
Message-ID: <3E3AFF5F.89C84069@digeo.com> (raw)
In-Reply-To: 200301312247.h0VMlxB09932@mail.osdl.org
Cliff White wrote:
>
> ...
> These loads suck up all the memory they can, so anything that gives us more
> free memory should
> be goodness. We think we are also seeing improvements in 2.5 in free memory,
> but
> we don't know for sure where is best to look and how best to prove it.
> Any advice?
Monitoring /proc/meminfo would be the main means. Further
info could be obtained by drilling down into /proc/vmstat
and /proc/slabinfo (the latter via bloatmeter, preferably).
http://www.zip.com.au/~akpm/linux/patches/stuff/
Martin Bligh is working on another VM reporting tool `vmtop', which
would be appropriate for that as well.
next prev parent reply other threads:[~2003-01-31 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030131141350.370c287a.akpm@digeo.com>
2003-01-31 22:47 ` [OSDL][BENCHMARK] OSDL-DBT-2 - 2.4 vs 2.5 4-way/8-way with vmstat Cliff White
2003-01-31 22:57 ` Andrew Morton [this message]
2003-01-31 20:26 Cliff White
2003-01-31 21:29 ` Andrew Morton
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=3E3AFF5F.89C84069@digeo.com \
--to=akpm@digeo.com \
--cc=cliffw@osdl.org \
--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