From: Andrew Morton <akpm@digeo.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: Bill Davidsen <davidsen@tmr.com>,
linux-kernel@vger.kernel.org, mbligh@aracnet.com, jw@pegasys.ws,
wa@almesberger.net, andersen@codepoet.org, woofwoof@hathway.com
Subject: Re: ps performance sucks
Date: Thu, 07 Nov 2002 13:05:45 -0800 [thread overview]
Message-ID: <3DCAD5A9.D4D4C1CB@digeo.com> (raw)
In-Reply-To: 200211072042.gA7KglX121245@saturn.cs.uml.edu
"Albert D. Cahalan" wrote:
>
> In case you happen to know where they are, I'm looking for these:
>
> pages reclaimed
/proc/vmstat:pgsteal
> minor faults
/proc/vmstat:pgfault - /proc/vmstat:pgmajfault
> COW faults
> zero-page faults
These are not available separately
> anticipated short-term memory shortfall
hm. tricky.
> pages freed
/proc/vmstat:pgfree
This is a little broken in 2.5.46. pgfree is accumulated
_before_ the per-cpu LIFO queues and pgalloc is accumulated _after_
the per-cpu queues (or vice versa) so they're out of whack.
> pages scanned by page-replacement algorithm
/proc/vmstat:pgscan
> clock cycles by page replacement algorithm
Not available. Could sum up the CPU across all kswapd instances,
which is a bit lame.
> number of system calls
Not available
> number of forks (fork, vfork, & clone) and execs
/proc/stat: processes
next prev parent reply other threads:[~2002-11-07 20:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 21:39 ps performance sucks Albert D. Cahalan
2002-11-05 22:46 ` Rik van Riel
2002-11-05 22:48 ` Robert Love
2002-11-05 23:23 ` Miquel van Smoorenburg
2002-11-05 23:37 ` Albert D. Cahalan
2002-11-05 23:37 ` Werner Almesberger
2002-11-06 0:10 ` Albert D. Cahalan
2002-11-06 1:29 ` Werner Almesberger
2002-11-07 17:19 ` Bill Davidsen
2002-11-07 20:42 ` Albert D. Cahalan
2002-11-07 21:05 ` Andrew Morton [this message]
2002-11-07 22:02 ` Albert D. Cahalan
2002-11-07 22:21 ` Andrew Morton
2002-11-08 21:05 ` Bill Davidsen
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=3DCAD5A9.D4D4C1CB@digeo.com \
--to=akpm@digeo.com \
--cc=acahalan@cs.uml.edu \
--cc=andersen@codepoet.org \
--cc=davidsen@tmr.com \
--cc=jw@pegasys.ws \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=wa@almesberger.net \
--cc=woofwoof@hathway.com \
/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