From: rwhron@earthlink.net
To: akpm@zip.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: tiobench
Date: Thu, 23 May 2002 09:10:23 -0400 [thread overview]
Message-ID: <20020523091023.A555@rushmore> (raw)
Andrew Morton wrote:
> tiobench sequential read throughput is enormously sensitive to the
> readahead setting. With the readahead at the default 128k
> with
>
> blockdev --setra 512 /dev/hda
>
> gives very nice throughput. But somehow 2.4.x seems to cheat
> and seems to do twice the readahead than the setting says, or something.
Bigger readahead helps dbench too.
Readahead in 2.5.x and dbench and tiobench sequential read
average throughput on my uniproc ide box was roughly:
kernel readahead dbench tiobench
2.5.0 - 2.5.7 8 8.1 mb/s 9.9 mb/s
2.5.8 - 2.5.10 0 3.5 mb/s 9.9 mb/s
2.5.11 - 2.5.17 256 13 mb/s 10.2 mb/s
2.5.8-akpm 1024 22 mb/s 18.1 mb/s
Bigger readahead appears to lower tiobench sequential read
latency a little.
2.4.x showed readahead = 8 for 2.4.3 - 2.4.19-pre8, including
aa, ac, jam, mjc, and rmap.
--
Randy Hron
reply other threads:[~2002-05-23 13:10 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=20020523091023.A555@rushmore \
--to=rwhron@earthlink.net \
--cc=akpm@zip.com.au \
--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