From: Steven Pratt <slpratt@austin.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: ext3 sequential write thoughput degrades in 2.5.72-mm1
Date: Mon, 23 Jun 2003 11:48:04 -0500 [thread overview]
Message-ID: <3EF72F44.1040109@austin.ibm.com> (raw)
Compared with 2.5.72 the mm1 tree drops off on sequential write
throughput for ext3. All other filesystems seem unaffected. This
degrade stays in mm2 and mm3. Do not have the data from 2.5.73 yet.
Full data can be found at:
http://ltcperf.ncsa.uiuc.edu/data/2.5.72-mm1/2.5.72-vs-2.5.72-mm1/
tolerance = 1.00 + 3.00% of 2.5.72
2.5.72 2.5.72-mm1
Theads MBs/sec MBs/sec %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 42.98 43.54 1.30 0.56 2.29
16 11.04 6.08 -44.93 -4.96 1.33 *
64 3.88 2.61 -32.73 -1.27 1.12 *
Results:Sequential Write CPU (Graph)
tolerance = 1.00 + 3.00% of 2.5.72
2.5.72 2.5.72-mm1
Theads %CPU %CPU %diff diff tolerance
---------- ------------ ------------ -------- ------------ ------------
1 53.32% 51.76% -2.93 -1.56 2.60
16 119.6% 86.11% -28.00 -33.49 4.59 *
64 37.23% 25.05% -32.72 -12.18 2.12 *
reply other threads:[~2003-06-23 16:32 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=3EF72F44.1040109@austin.ibm.com \
--to=slpratt@austin.ibm.com \
--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