public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 2.6.30-rc deadline scheduler performance regression for iozone over NFS
Date: Mon, 11 May 2009 18:58:26 +0200	[thread overview]
Message-ID: <20090511165826.GG4694@kernel.dk> (raw)
In-Reply-To: <x49skjb21b7.fsf@segfault.boston.devel.redhat.com>

On Mon, May 11 2009, Jeff Moyer wrote:
> Jens Axboe <jens.axboe@oracle.com> writes:
> 
> > On Fri, May 08 2009, Andrew Morton wrote:
> >> On Thu, 23 Apr 2009 10:01:58 -0400
> >> Jeff Moyer <jmoyer@redhat.com> wrote:
> >> 
> >> > Hi,
> >> > 
> >> > I've been working on CFQ improvements for interleaved I/Os between
> >> > processes, and noticed a regression in performance when using the
> >> > deadline I/O scheduler.  The test uses a server configured with a cciss
> >> > array and 1Gb/s ethernet.
> >> > 
> >> > The iozone command line was:
> >> >   iozone -s 2000000 -r 64 -f /mnt/test/testfile -i 1 -w
> >> > 
> >> > The numbers in the nfsd's row represent the number of nfsd "threads".
> >> > These numbers (in MB/s) represent the average of 5 runs.
> >> > 
> >> >                v2.6.29
> >> > 
> >> > nfsd's  |   1    |  2   |   4   |   8
> >> > --------+---------------+-------+------
> >> > deadline| 43207 | 67436 | 96289 | 107590
> >> > 
> >> >               2.6.30-rc1
> >> > 
> >> > nfsd's  |   1   |   2   |   4   |   8
> >> > --------+---------------+-------+------
> >> > deadline| 43732 | 68059 | 76659 | 83231
> >> > 
> >> >     2.6.30-rc3.block-for-linus
> >> > 
> >> > nfsd's  |   1   |   2   |   4   |   8
> >> > --------+---------------+-------+------
> >> > deadline| 46102 | 71151 | 83120 | 82330
> >> > 
> >> > 
> >> > Notice the drop for 4 and 8 threads.  It may be worth noting that the
> >> > default number of NFSD threads is 8.
> >> > 
> >> 
> >> I guess we should ask Rafael to add this to the post-2.6.29 regression
> >> list.
> >
> > I agree. It'd be nice to bisect this one down, I'm guessing some mm
> > change has caused this writeout regression.
> 
> It's not writeout, it's a read test.

Doh sorry, I even ran these tests as well a few weeks back. So perhaps
some read-ahead change, I didn't look into it. FWIW, on a single SATA
drive here, it didn't show any difference.

-- 
Jens Axboe


  reply	other threads:[~2009-05-11 16:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 14:01 2.6.30-rc deadline scheduler performance regression for iozone over NFS Jeff Moyer
2009-05-08 19:01 ` Andrew Morton
2009-05-11  8:14   ` Jens Axboe
2009-05-11 13:53     ` Jeff Moyer
2009-05-11 16:58       ` Jens Axboe [this message]
2009-05-13  3:29         ` Jeff Moyer
2009-05-13  3:44           ` Andrew Morton
2009-05-13 14:58             ` Jeff Moyer
2009-05-13 16:20               ` Olga Kornievskaia
2009-05-13 16:32                 ` Andrew Morton
2009-05-13 18:16                   ` Olga Kornievskaia
2009-05-13 19:06                     ` Jeff Moyer
2009-05-13 18:25                   ` Jim Rees
2009-05-13 19:45                     ` Trond Myklebust
2009-05-13 19:29               ` Jeff Moyer
2009-05-13 23:45                 ` Trond Myklebust
2009-05-14 13:34                   ` Jeff Moyer
2009-05-14 14:33                     ` Trond Myklebust
2009-05-14 14:38                       ` Jeff Moyer
2009-05-14 15:00                       ` Jeff Moyer
2009-05-17 19:10                         ` Trond Myklebust
2009-05-17 19:12                           ` Trond Myklebust
2009-05-18 14:15                             ` Jeff Moyer
2009-05-22 23:45                               ` J. Bruce Fields
2009-05-14 17:55                   ` J. Bruce Fields
2009-05-14 18:26                     ` Trond Myklebust
2009-05-15 21:37                       ` J. Bruce Fields

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=20090511165826.GG4694@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=jmoyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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