From: Andrew Morton <akpm@osdl.org>
To: Judith Lebzelter <judith@osdl.org>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: OSDL aio-stress results on latest kernels show buffered random read issue
Date: Wed, 29 Sep 2004 20:46:28 -0700 [thread overview]
Message-ID: <20040929204628.0ffdf10e.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0409291621170.4332-100000@osdlab.pdx.osdl.net>
Judith Lebzelter <judith@osdl.org> wrote:
>
> Hello;
>
> I am running aio-stress on the most recent kernels and have
> found that on linux-2.6.8, 2.6.9-rc2 and 2.6.9-rc2-mm4 the
> performance of buffered random reads is poor compared to the
> buffered random writes:
>
> 2.6.8 2.6.9-rc2 2.6.9-rc2-mm4
> --------------------------------------------
> random write 35.66 MB/s 34.80 MB/s 29.89 MB/s
> random read 7.69 MB/s 7.50 MB/s 7.68 MB/s
>
> ** 2CPU hosts with striped Megaraid. 1G RAM. 4G File.
>
>
> This shows up on our 4CPU host as well. (striped AACRAID.4G
> RAM. 8G File):
> 2.6.9-rc2 2.6.9-rc2-mm4 2.6.9-rc2-mm1
> -------------------------------------------
> random write 31.36 MB/s 18.92 MB/s 18.97 MB/s
> random read 11.13 MB/s 9.74 MB/s 11.05 MB/s
>
>
> There seems to be an issue with the reads. Usually, reads
> should be at least as fast as writes of the same type.
>
> Also, there seems to be a substantial drop-off in the performance
> of AIO buffered-random writes in the mm kernels. (14% on 2CPU,
> 40% on 4CPU)
>
Well one would expect writes to be much faster than reads because writes
usually do not involve performing physical I/O, and when pagecache
writeback finally happens it has vastly more data to work with and hence
can schedule I/O more efficiently.
Unless you are using O_SYNC or fsync(), in which case ignore the above.
The regression within random write performance is unexpected. Can you
please provide a URL to the current version of the test tool, and a
description of how you are invoking it? What sort of I/O system, what
filesystem, etc.
Thanks.
next prev parent reply other threads:[~2004-09-30 0:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 23:29 OSDL aio-stress results on latest kernels show buffered random read issue Judith Lebzelter
2004-09-30 0:44 ` William Lee Irwin III
2004-09-30 22:00 ` Judith Lebzelter
2004-09-30 3:46 ` Andrew Morton [this message]
2004-09-30 17:48 ` Judith Lebzelter
2004-09-30 18:54 ` 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=20040929204628.0ffdf10e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=judith@osdl.org \
--cc=linux-aio@kvack.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