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: Wed, 7 Oct 2009 12:52:59 +0200 [thread overview]
Message-ID: <20091007105259.GD8703@kernel.dk> (raw)
In-Reply-To: <x49y6no8jxw.fsf@segfault.boston.devel.redhat.com>
On Tue, Oct 06 2009, Jeff Moyer wrote:
> >> 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.
>
> I'd love it if you could run some benchmarks, thank you!
So here's a pretty basic test. It does random reads from a bunch of
devices, I tested both 4kb and 64kb block sizes. Queue depth used is 32
for both cases, but note that this test uses a thread per device (so the
queue depth is 32 per device). Results are averaged over 3 runs.
slat/clat are the submission and completion latencies, they are in
microseconds here.
4kb random reads
kernel sys IOPS slat clat
----------------------------------------------------
2.6.32-rc3+patch 25.8% 192500 7.9 2606
2.6.32-rc3 27.4% 191300 8.4 2612
64kb random reads
kernel sys IOPS slat clat
----------------------------------------------------
2.6.32-rc3+patch 2.5% 24590 9.7 9681
2.6.32-rc3 2.5% 24580 9.4 9691
So pretty close, nothing earth shattering here. What the results above
do not show is that the 4kb test runs very stable with your patch.
Mainline fluctuates somewhat in the bandwidth, most likely due to the
varying depth.
--
Jens Axboe
next prev parent reply other threads:[~2009-10-07 10:53 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
2009-10-06 18:18 ` Jeff Moyer
2009-10-07 10:52 ` Jens Axboe [this message]
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=20091007105259.GD8703@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox