From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Benchmarking objrmap under memory pressure
Date: Wed, 14 Apr 2004 14:11:34 -0400 [thread overview]
Message-ID: <c5jumv$men$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <20040413005111.71c7716d.akpm@osdl.org>
Andrew Morton wrote:
> "Martin J. Bligh" <mbligh@aracnet.com> wrote:
>
>>UP Athlon 2100+ with 512Mb of RAM. Rebooted clean before each test
>>then did "make clean; make vmlinux; make clean". Then I timed a
>>"make -j 256 vmlinux" to get some testing under mem pressure.
>>
>>I was trying to test the overhead of objrmap under memory pressure,
>>but it seems it's actually distinctly negative overhead - rather pleasing
>>really ;-)
>>
>>2.6.5
>>225.18user 30.05system 6:33.72elapsed 64%CPU (0avgtext+0avgdata 0maxresident)k
>>0inputs+0outputs (37590major+2604444minor)pagefaults 0swaps
>>
>>2.6.5-anon_mm
>>224.53user 26.00system 5:29.08elapsed 76%CPU (0avgtext+0avgdata 0maxresident)k
>>0inputs+0outputs (29127major+2577211minor)pagefaults 0swaps
>
>
> A four second reduction in system time caused a one minute reduction in
> runtime? Pull the other one ;)
I was looking at the pagefault counts, myself. I'd like to see disk io
counts for each run, that sometimes brings enlightenment. Maybe do 20
sec counts with diorate or some such.
(http://pages.prodigy.net/davidsen/ if you don't have your own favorite
tool)
>
> Average of five runs, please...
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
prev parent reply other threads:[~2004-04-14 18:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 7:39 Benchmarking objrmap under memory pressure Martin J. Bligh
2004-04-13 7:51 ` Andrew Morton
2004-04-13 7:55 ` Martin J. Bligh
2004-04-13 21:59 ` Andrea Arcangeli
2004-04-14 0:38 ` Martin J. Bligh
2004-04-14 16:27 ` Andrea Arcangeli
2004-04-14 16:42 ` Martin J. Bligh
2004-04-14 17:11 ` Andrea Arcangeli
2004-04-14 17:48 ` Hugh Dickins
2004-04-14 23:39 ` Andrea Arcangeli
2004-04-15 10:21 ` Hugh Dickins
2004-04-15 13:22 ` Andrea Arcangeli
2004-04-15 13:45 ` Hugh Dickins
2004-04-15 14:08 ` Andrea Arcangeli
2004-04-15 16:23 ` Bill Davidsen
2004-04-15 16:48 ` Hugh Dickins
2004-04-22 19:54 ` Bill Davidsen
2004-04-22 21:26 ` Hugh Dickins
2004-04-14 18:11 ` Bill Davidsen [this message]
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='c5jumv$men$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.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