All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: zach.brown@oracle.com, linux-aio <linux-aio@kvack.org>,
	Linux Kernel Mailing <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch v4 0/3] aio: implement request batching [more performance numbers]
Date: Tue, 6 Oct 2009 20:06:28 +0200	[thread overview]
Message-ID: <20091006180628.GB5216@kernel.dk> (raw)
In-Reply-To: <x49eipga02o.fsf@segfault.boston.devel.redhat.com>

On Tue, Oct 06 2009, Jeff Moyer wrote:
> Here's a mail I got from Nathan Roberts.
> 
> Cheers,
> Jeff
> 
> ---
> 
> Similar test as before. I had to re-upload the files so comparing
> against last time isn't really apples-apples.
> 
> Disk is a cciss logical drive consisting of 12 SATA drives in a RAID6
> configuration with 128K stripes.
> 
> Test case 1 is to read 1 million random 40K files (no file is read
> more than once), 16 4K iocbs at a time, 100 threads.
> 
> Test case 2 is the same except 100,000 128K files are read.
> 
> Unit of measure is "files read per second".
> 
> 
> 40K
> -------------------------------------------------
> Kernel                              NOOP
> ------                              ----
> 2.6.30.5                            682
> 2.6.30.5 (w/o drop_caches)          718
> 2.6.30.5+patch_v4                   900
> 2.6.30.5+patch_v4 (w/o drop caches) 965
> 
> 
> 128K
> -------------------------------------------------
> Kernel                              NOOP
> ------                              ----
> 2.6.30.5                            242
> 2.6.30.5 (w/o drop_caches)          350
> 2.6.30.5+patch_v4                   292
> 2.6.30.5+patch_v4 (w/o drop caches) 420

Nice numbers! The patch looks good to me from a quick look, if you want
I can throw it into the testing mix tomorrow and see what kind of
improvements I see here. With performance increase of that magnitude, we
should get it in sooner rather than later.

-- 
Jens Axboe


  reply	other threads:[~2009-10-06 18:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 22:54 [patch v4 0/3] aio: implement request batching Jeff Moyer
2009-10-02 22:56 ` [patch v4 1/2] block: get rid of the WRITE_ODIRECT flag Jeff Moyer
2009-10-02 22:57 ` [patch v4 2/2] aio: implement request batching Jeff Moyer
2009-10-02 22:58 ` [patch v4 0/3] " Jeff Moyer
2009-10-06 17:45 ` [patch v4 0/3] aio: implement request batching [more performance numbers] Jeff Moyer
2009-10-06 18:06   ` Jens Axboe [this message]
2009-10-06 18:18     ` Jeff Moyer
2009-10-07 10:52       ` Jens Axboe
2009-10-07 12:09         ` Jeff Moyer
2009-10-27 16:16         ` Jeff Moyer
2009-10-28  8:28           ` Jens Axboe

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=20091006180628.GB5216@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=jmoyer@redhat.com \
    --cc=linux-aio@kvack.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zach.brown@oracle.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 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.