From: Steven Pratt <slpratt@austin.ibm.com>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@digeo.com>
Subject: Re: 2.5.70-mm2 causes performance drop of random read O_DIRECT
Date: Wed, 11 Jun 2003 10:16:13 -0500 [thread overview]
Message-ID: <3EE747BD.6010408@austin.ibm.com> (raw)
In-Reply-To: 3EE67F38.9030702@cyberone.com.au
Nick Piggin wrote:
> Steven Pratt wrote:
>
>> Nick Piggin wrote:
>>
>>> Steven Pratt wrote:
>>>
>>>> Starting in 2.5.70-mm2 and continuing in the mm tree, there is a
>>>> significant degrade in random read for block devices using
>>>> O_DIRECT. The drop occurs for all block sizes and ranges from
>>>> 30%-40. CPU usage is also lower although it may already be so low
>>>> as to be irrelavent.
>>>
>>> Hi Steven, this is quite likely to be an io scheduler problem.
>>> Is your test program rawread v2.1.5?
>>
>> This test was actually using 2.1.4, but the only difference in the
>> 2.1.5 version is a fix for the test label array for the aio versions
>> of the test. No functional change, just fixed the outputed test
>> description.
>>
>>> What is the command line you are using to invoke the program?
>>
>> rawread -t6 -p8 -m1 -d2 -s4096 -n65536 -l1 -z -x
>>
>> Which you can find if you follow either results link and look in the
>> benchmark directory where all raw benchmark out put is stored.
>
> OK thanks, I can now reproduce this! I'll work on it.
Looks like Andrew beat you to it. Both 2.5.70-mm7 and mm8 are back up
to the previous performance levels for random reads.
Steve
next prev parent reply other threads:[~2003-06-11 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 23:32 2.5.70-mm2 causes performance drop of random read O_DIRECT Steven Pratt
2003-06-10 0:13 ` Nick Piggin
2003-06-10 14:05 ` Steven Pratt
2003-06-11 1:00 ` Nick Piggin
2003-06-11 15:16 ` Steven Pratt [this message]
2003-06-12 1:14 ` Nick Piggin
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=3EE747BD.6010408@austin.ibm.com \
--to=slpratt@austin.ibm.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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