From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: piotr@larroy.com, linux-kernel@vger.kernel.org
Subject: Re: CFQ iosched praise: good perfomance and better latency
Date: Mon, 19 Apr 2004 16:12:56 +1000 [thread overview]
Message-ID: <40836DE8.5080303@yahoo.com.au> (raw)
In-Reply-To: <20040418225752.56d10695.akpm@osdl.org>
Andrew Morton wrote:
> Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>
>>Pedro Larroy wrote:
>>
>>>Hi
>>>
>>>I've been trying CFQ ioscheduler in my software raid5 with nice results,
>>>I've observed that a latency pattern still exists, just as in the
>>>anticipatory ioscheduler, but those spikes are now much lower (from
>>>6ms with AS to 2ms with CFQ as seen in the bottom of
>>>http://pedro.larroy.com/devel/iolat/analisys/),
>>>plus apps seems to get a fair amount of io so they don't get starved.
>>>
>>>Seems a good choice for io loaded boxes. Thanks Jens Axboe.
>>>
>>
>>Although AS isn't at its best when behind raid devices (it should
>>probably be in front of them), you could be seeing some problem
>>with the raid code.
>>
>>I'd be interested to see what the graph looks like with elevator=noop
>
>
> This isn't a very surprising result, is it? AS throws away latency to gain
> throughput. Pedro is measuring latency...
>
Well I think Pedro actually means *seconds*, not ms. The URL
shows AS peaks at nearly 10 seconds latency, and CFQ over 2s.
It really seems like a raid problem though, because latency
measured at the individual devices is under 250ms for AS.
next prev parent reply other threads:[~2004-04-19 6:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 0:56 CFQ iosched praise: good perfomance and better latency Pedro Larroy
2004-04-19 5:10 ` Nick Piggin
2004-04-19 5:57 ` Andrew Morton
2004-04-19 6:12 ` Nick Piggin [this message]
2004-04-19 11:32 ` Pedro Larroy
2004-04-19 11:53 ` Nick Piggin
2004-04-19 23:59 ` Pedro Larroy
2004-04-19 13:27 ` Daniel Pittman
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=40836DE8.5080303@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piotr@larroy.com \
/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