From: Suparna Bhattacharya <suparna@in.ibm.com>
To: theonetruekenny@yahoo.com
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org
Subject: AIO performance
Date: Fri, 17 Mar 2006 18:58:26 +0530 [thread overview]
Message-ID: <20060317132826.GA3726@in.ibm.com> (raw)
Hello Kenny,
In browsing lkml archives today I came across your query about
AIO performance and conclusions from our 2003 paper. I am sorry, I
missed your post at that time (it may be a good idea to cc
linux-aio@kvack.org on AIO related queries in addition to lkml).
The results in the 2003 paper were based on a specific microbenchmark,
but (as mentioned later in the conclusion) it couldn't capture the
impact of well designed AIO usage which can actually improve the overall
efficiency of an application. In my own experience later, and following
further performance tuning of AIO, I found the case of streaming
random AIO reads and writes to be the most interesting, as it can provide
throughput gains while simplifying the coordination model. This is the
pattern seen under some database workloads.
There is in fact a more recent reference you could look at, which is
a follow-on paper at OLS 2004 on Linux 2.6 AIO Performance and Robustness,
(http://www.linuxsymposium.org/proceedings/reprints/Reprint-Bhattacharya-OLS2004.pdf)
where we published some real application performance numbers as well
as microbenchmark results for streaming AIO reads/writes using aio-stress
(instead of rawiobench). You may find that interesting. AIO resulted in
close to 10% performance gain for our database benchmark run, but more
significantly as we observed, a single page cleaner thread using AIO was
able to drive around 40% more writes than 55 page cleaner threads without AIO.
I hope that helps.
Regards
Suparna
--
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Lab, India
reply other threads:[~2006-03-17 13:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060317132826.GA3726@in.ibm.com \
--to=suparna@in.ibm.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=theonetruekenny@yahoo.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