From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: iozone write 50% regression in kernel 2.6.24-rc1
Date: Mon, 12 Nov 2007 14:26:20 +0100 [thread overview]
Message-ID: <1194873980.7179.31.camel@twins> (raw)
In-Reply-To: <1194861112.20251.124.camel@ymzhang>
[-- Attachment #1: Type: text/plain, Size: 2138 bytes --]
Single socket, dual core opteron, 2GB memory
Single SATA disk, ext3
x86_64 kernel and userland
(dirty_background_ratio, dirty_ratio) tunables
---- (5,10) - default
2.6.23.1-42.fc8 #1 SMP
524288 4 59580 60356
524288 4 59247 61101
524288 4 61030 62831
2.6.24-rc2 #28 SMP PREEMPT
524288 4 49277 56582
524288 4 50728 61056
524288 4 52027 59758
524288 4 51520 62426
---- (20,40) - similar to your 8GB
2.6.23.1-42.fc8 #1 SMP
524288 4 225977 447461
524288 4 232595 496848
524288 4 220608 478076
524288 4 203080 445230
2.6.24-rc2 #28 SMP PREEMPT
524288 4 54043 83585
524288 4 69949 516253
524288 4 72343 491416
524288 4 71775 492653
---- (60,80) - overkill
2.6.23.1-42.fc8 #1 SMP
524288 4 208450 491892
524288 4 216262 481135
524288 4 221892 543608
524288 4 202209 574725
524288 4 231730 452482
2.6.24-rc2 #28 SMP PREEMPT
524288 4 49091 86471
524288 4 65071 217566
524288 4 72238 492172
524288 4 71818 492433
524288 4 71327 493954
While I see that the write speed as reported under .24 ~70MB/s is much
lower than the one reported under .23 ~200MB/s, I find it very hard to
believe my poor single SATA disk could actually do the 200MB/s for
longer than its cache 8/16 MB (not sure).
vmstat shows that actual IO is done, even though the whole 512MB could
fit in cache, hence my suspicion that the ~70MB/s is the most realistic
of the two.
I'll have to look into what iozone actually does though and why this
patch makes the output different.
FWIW - because its a single backing dev it does get to 100% of the dirty
limit after a few runs, so not sure what makes the difference.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-11-12 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 9:47 iozone write 50% regression in kernel 2.6.24-rc1 Zhang, Yanmin
2007-11-09 9:54 ` Peter Zijlstra
2007-11-12 2:14 ` Zhang, Yanmin
2007-11-12 9:45 ` Peter Zijlstra
2007-11-12 9:51 ` Zhang, Yanmin
2007-11-12 13:26 ` Peter Zijlstra [this message]
[not found] ` <47386BC4.3050403@panasas.com>
2007-11-12 16:48 ` Peter Zijlstra
2007-11-13 2:19 ` Zhang, Yanmin
2007-11-13 8:34 ` Zhang, Yanmin
2007-11-13 18:32 ` Peter Zijlstra
2007-11-12 17:25 ` Mark Lord
2007-11-13 1:49 ` Zhang, Yanmin
-- strict thread matches above, loose matches on Subject: below --
2007-11-09 12:36 Martin Knoblauch
2007-11-12 0:45 ` Zhang, Yanmin
2007-11-12 12:58 Martin Knoblauch
2007-11-13 2:04 ` Zhang, Yanmin
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=1194873980.7179.31.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=yanmin_zhang@linux.intel.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