From: Steven Pratt <slpratt@austin.ibm.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Vladimir Saveliev <vs@namesys.com>,
reiserfs-list@namesys.com, reiserfs-dev@namesys.com
Subject: Re: dbench regression in 2.6
Date: Mon, 08 Sep 2003 15:34:59 -0500 [thread overview]
Message-ID: <3F5CE7F3.8070303@austin.ibm.com> (raw)
In-Reply-To: <3F5CE24B.6020706@namesys.com>
Hans Reiser wrote:
> Steven Pratt wrote:
>
>> Ok, first let me start with appologies as this turns out to be a wild
>> goose chase. It seems that I am running the version of reiserfsprogs
>> that ships with SLES 8.0 (3.6.2) which has a hardcoded check for
>> kernel versions 2.2, 2.4 and 2.5, but does not know about 2.6 and
>> thus the mkfs.resiserfs is failing. Since all of this testing is
>> automated this failure was not caught, and the dbench numbers
>> reported were actually for the last filesystem run on that drive, in
>> this case XFS (which is why it looks so bad :-) ). I have fixed the
>> scripts to force the format to 3.6 and all seems to be well. If I
>> get the chance I will go backfill all of the numbers. Sorry for the
>> confusion but I run these regresion tests in my spare time and don't
>> always have time to crawl through the output, although a simple look
>> in the captured /proc/mounts, or even the fstype file I create in the
>> benchmark directory would have saved us all a lot of time.
>> Again, sorry for the confusion, keep up the good work.
>>
>> Steve
>>
>>
>>
> Steve, thanks a lot for making this effort. I would be interested in
> your results. Do you think it might be possible for us to test and
> profile reiser4 scalability on your 8-way? We designed reiser4 to be
> highly scalable, but of course one always finds a few unexpected
> scalability issues when one tests for the first time.
Yes, I definitely plan on doing reiser4 benchmarking. Just a matter of
finding some time to do it.
Steve
next prev parent reply other threads:[~2003-09-08 20:34 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
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 [this message]
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=3F5CE7F3.8070303@austin.ibm.com \
--to=slpratt@austin.ibm.com \
--cc=reiser@namesys.com \
--cc=reiserfs-dev@namesys.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.