linux-kernel - Re: [patch v4 0/3] aio: implement request batching [more performance numbers]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 7 Oct 2009 12:52:59 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Jeff Moyer <jmoyer@...hat.com>
Cc:	zach.brown@...cle.com, linux-aio <linux-aio@...ck.org>,
	Linux Kernel Mailing <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [patch v4 0/3] aio: implement request batching [more
	performance numbers]

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/