From: Steven Pratt <slpratt@austin.ibm.com>
To: Vladimir Saveliev <vs@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: dbench regression in 2.6
Date: Thu, 04 Sep 2003 09:23:42 -0500 [thread overview]
Message-ID: <3F574AEE.7080402@austin.ibm.com> (raw)
In-Reply-To: <200309041138.40795.vs@namesys.com>
Vladimir Saveliev wrote:
>Hi
>
>On Wednesday 03 September 2003 23:04, Hans Reiser wrote:
>
>
>>Steven Pratt wrote:
>>
>>
>>
>>>Is anyone looking into the dbench multitheaded regression in 2.6 that I
>>>reported here a couple of weeks ago?
>>>
>>>
>
>Sorry, I was unable to find your report in mail archives. Could you, please,
>remind what is the problem?
>
> I don't see any change in the
>
>
>>>latest trees.
>>>
>>>
>>>
The problem showed up in 2.6.0-test1, and every kernel since. The
problem is that from 2.5.65 (earliest data I have) to 2.5.69 dbench on
reiserfs with 16 clients got a throughput of ~200MB/sec. In 2.5.70
through 2.5.75 the score went up to ~280MB/sec, a good thing. But in
2.6.0-test1 the throughput dropped to below 50 MB/sec. Since then it
has risen slightly but still at only around 60MB/sec. Single client
dbench showed similar, although much less dramatic changes. No other
file system exhibited a change in the 2.6.0-test1 kernel so this seems
to be unique to reiserfs.
>>>
>>>
>http://ausgsa.ibm.com/projects/l/ltcperformance/2003benchmarks/regression/results/history-graphs/dbench.reiser.throughput.plot.16.png
>
>
>
>Is this address right?
>
No, my bad. Right address is
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/dbench.reiser.throughput.plot.16.png
see also
http://ltcperf.ncsa.uiuc.edu/data/history-graphs/dbench.reiser.throughput.plot.1.png
Also if you go to
http://ltcperf.ncsa.uiuc.edu/data/2.6.0-test1/2.5.75-vs-2.6.0-test1/index.html
and select the results links related to dbench resierfs you can find
kernel profile, sar data and lots of other system information which may
help in isolating the problem.
Steve
next prev parent reply other threads:[~2003-09-04 14:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 18:46 dbench regression in 2.6 Steven Pratt
2003-09-03 19:43 ` Mike Fedyk
2003-09-03 22:42 ` Mike Fedyk
2003-09-04 14:13 ` Steven Pratt
[not found] ` <3F563B3B.6060406@namesys.com>
2003-09-04 7:38 ` Vladimir Saveliev
2003-09-04 14:23 ` Steven Pratt [this message]
2003-09-04 17:58 ` Mike Fedyk
2003-09-05 15:24 ` Steven Pratt
2003-09-05 15:49 ` Hans Reiser
2003-09-08 17:05 ` Vladimir Saveliev
2003-09-08 18:02 ` Steven Pratt
2003-09-08 19:55 ` Steven Pratt
2003-09-08 20:10 ` Hans Reiser
2003-09-08 20:34 ` Steven Pratt
2003-09-09 10:35 ` Nikita Danilov
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=3F574AEE.7080402@austin.ibm.com \
--to=slpratt@austin.ibm.com \
--cc=reiserfs-list@namesys.com \
--cc=vs@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.