From: rwhron@earthlink.net
To: davej@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] (1/2) reverse mapping VM for 2.5.23 (rmap-13b)
Date: Tue, 25 Jun 2002 06:58:37 -0400 [thread overview]
Message-ID: <20020625105837.GA12264@rushmore> (raw)
> Maybe Randy Hron (added to Cc) can find some spare time
> to benchmark these sometime before the summit too[1].
dbench isn't scaling as well with the -rmap13b patch.
With 128 processes, dbench throughput is less than 1/3
of mainline.
dbench ext2 32 processes Average High Low
2.5.24 28.24 28.84 27.30 mb/sec
2.5.24-rmap13b 21.64 23.50 19.71
dbench ext2 128 processes Average High Low
2.5.24 19.32 21.05 18.05
2.5.24-rmap13b 5.34 5.38 5.30
tiobench:
Sequential reads, rmap had about 10% more throughput
and lower max latency.
For random reads, throughput was lower and max latency
was higher with rmap.
Lmbench:
Most metrics look better with rmap. Exceptions
are fork/exec latency and mmap latency. mmap
latency was 18% higher with rmap.
Autoconf build (fork test) was about 5% faster
without rmap.
Details at:
http://home.earthlink.net/~rwhron/kernel/latest.html
--
Randy Hron
next reply other threads:[~2002-06-25 10:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 10:58 rwhron [this message]
2002-06-25 21:57 ` [PATCH] (1/2) reverse mapping VM for 2.5.23 (rmap-13b) Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2002-06-20 14:20 rwhron
2002-06-20 4:07 rwhron
2002-06-20 12:47 ` Dave Jones
2002-06-19 11:18 Craig Kulesa
2002-06-19 16:18 ` Andrew Morton
2002-06-19 17:00 ` Daniel Phillips
2002-06-19 17:11 ` Dave Jones
2002-06-19 17:35 ` Rik van Riel
2002-06-19 19:53 ` Ingo Molnar
2002-06-19 20:21 ` Craig Kulesa
2002-06-19 20:24 ` Linus Torvalds
2002-06-24 21:34 ` Martin J. Bligh
2002-06-24 21:39 ` Rik van Riel
2002-06-24 21:56 ` Martin J. Bligh
2002-07-04 5:19 ` Daniel Phillips
2002-06-24 15:02 ` Rik van Riel
2002-06-19 19:04 ` Steven Cole
2002-06-19 22:44 ` William Lee Irwin III
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=20020625105837.GA12264@rushmore \
--to=rwhron@earthlink.net \
--cc=davej@suse.de \
--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