From: Suparna Bhattacharya <suparna@in.ibm.com>
To: linux-aio@kvack.org, linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: aio-stress throughput regressions from 2.6.11 to 2.6.12
Date: Fri, 1 Jul 2005 13:26:00 +0530 [thread overview]
Message-ID: <20050701075600.GC4625@in.ibm.com> (raw)
Has anyone else noticed major throughput regressions for random
reads/writes with aio-stress in 2.6.12 ?
Or have there been any other FS/IO regressions lately ?
On one test system I see a degradation from around 17+ MB/s to 11MB/s
for random O_DIRECT AIO (aio-stress -o3 testext3/rwfile5) from 2.6.11
to 2.6.12. It doesn't seem filesystem specific. Not good :(
BTW, Chris/Ben, it doesn't look like the changes to aio.c have had an impact
(I copied those back to my 2.6.11 tree and tried the runs with no effect)
So it is something else ...
Ideas/thoughts/observations ?
Regards
Suparna
--
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Lab, India
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org. For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next reply other threads:[~2005-07-01 7:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 7:56 Suparna Bhattacharya [this message]
2005-07-01 14:25 ` aio-stress throughput regressions from 2.6.11 to 2.6.12 Benjamin LaHaise
2005-07-06 4:30 ` Suparna Bhattacharya
2005-07-08 17:58 ` Benjamin LaHaise
2005-07-05 14:00 ` Chris Mason
2005-07-05 16:12 ` Benjamin LaHaise
2005-07-06 10:37 ` Suparna Bhattacharya
2005-07-06 12:10 ` aio-stress regressions in 2.6.12 narrowed down to AIC7xxx Suparna Bhattacharya
2005-07-11 7:43 ` aio-stress throughput regressions from 2.6.11 to 2.6.12 Sébastien Dugué
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=20050701075600.GC4625@in.ibm.com \
--to=suparna@in.ibm.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).