All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: "Ananiev, Leonid I" <leonid.i.ananiev@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Cfq  first request patch changes IO performance
Date: Tue, 27 Feb 2007 21:39:54 +0100	[thread overview]
Message-ID: <20070227203954.GI3733@kernel.dk> (raw)
In-Reply-To: <B41635854730A14CA71C92B36EC22AAC872B21@mssmsx411>

On Mon, Feb 26 2007, Ananiev, Leonid I wrote:
> The patch "cfq-iosched: defer slice activation to first request being
> active"
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=c
> ommitdiff;h=44f7c16065c83060cbb9dd9b367141682a6e2b8e;hp=99f9628aba4d8fb3
> b8d955c9efded0d0a1995fad
> 
> Sysbench fileio (random read/write mix)	-15%
> Tiobench sequential write		-3%
> Tiobench random write 			-5%
> Iozone record re-write			-21%
> Iozone mmap sequential read 		-20%
> Iozone mmap random write		+45%
> Aio-stress direct sequential read		+29%
> For other 3 tiobench, 7 aiostress and 13 iozone tests the result changes
> are less than variation.
> 
> Considered patch does not impact on performance if all threads have
> equal IO activity (tiobench).
> If single thread has IO activity the performance becomes unstable and is
> decreased mainly.

Yep there are a few unfortunate side effects, I have later fixed those.
I just need to split that patchset up and commit it.

-- 
Jens Axboe


      reply	other threads:[~2007-02-27 20:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-26 13:08 Cfq first request patch changes IO performance Ananiev, Leonid I
2007-02-27 20:39 ` Jens Axboe [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=20070227203954.GI3733@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=leonid.i.ananiev@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.