public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
To: linux-kernel@vger.kernel.org
Subject: Re: CFQ iosched praise: good perfomance and better latency
Date: Mon, 19 Apr 2004 23:27:09 +1000	[thread overview]
Message-ID: <87r7ukksia.fsf@enki.rimspace.net> (raw)
In-Reply-To: 40835F4E.5000308@yahoo.com.au

On Mon, 19 Apr 2004, Nick Piggin 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.

Hrm.  So, if AS isn't a good to have behind RAID devices, but is
reasonable before them, is there any easy way to configure a system like
that?

I don't see an easy way to change the IO scheduler on a per-device basis
anywhere...

        Daniel


-- 
A wonderful discovery, psychoanalysis.  
Makes quite simple people feel they're complex.
        -- S. N. Behrman


      parent reply	other threads:[~2004-04-19 13:46 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
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 [this message]

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=87r7ukksia.fsf@enki.rimspace.net \
    --to=daniel@rimspace.net \
    --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