From: reiser <reiser@namesys.com>
To: Cliff White <cliffw@osdl.org>
Cc: linux-kernel@vger.kernel.org, reiserfs-list@namesys.com,
Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>,
Oleg Drokin <green@namesys.com>,
Nikita Danilov <Nikita@namesys.com>
Subject: Re: We need help benchmarking and debugging reiser4
Date: Sat, 02 Nov 2002 17:09:09 -0800 [thread overview]
Message-ID: <3DC47735.9060206@namesys.com> (raw)
In-Reply-To: <200211012236.gA1MaqT20507@mail.osdl.org>
Cliff White wrote:
>>Can some of you help us by doing such things as replicating our
>>benchmarks, and helping us debug it as we enter the last stretch before
>>Halloween?
>>
>>
>>
>
>We are interested in helping, but i haven't seen the follow-up mail
>mentioned below - if you could send us some more specifics, we'd be
>glad to join the fun.
>cliffw
>OSDL
>
>
>
>>Nikita and Oleg will describe the details of what to do to replicate the
>>benchmarks, please be sure to use reiser4 readdir order for writes to
>>reiser4 (that means don't use tarballs made from ext2 (Remember that
>>writes determine subsequent read performance.)), and to use the latest
>>hard drives and fast processors with udma 5 turned on. We are quite
>>sensitive to transfer speed since we do a good job of avoiding seeks.
>>We are sensitive to readdir order because we sort directory entries
>>(which is necessary for having efficient large directory lookups). In
>>reiser4.1 we will ship a repacker, and then it won't matter what order
>>you do writes in so long as the repacker gets a chance to run at night.
>>
>>--
>>Hans
>>
>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>>Please read the FAQ at http://www.tux.org/lkml/
>>
>>
>>
>
>
>
>
>
>
Cliff, has there been a russian timezone working day since you requested
it? (I don't have access to your original email at the moment.) If
there has been, then Nikita, please explain why the request was lost,
and assure me that next time it goes into someone's todo list, and gets
responded to on the same day.
Hans
next prev parent reply other threads:[~2002-11-03 1:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 8:30 We need help benchmarking and debugging reiser4 Hans Reiser
2002-11-01 22:36 ` Cliff White
2002-11-03 1:09 ` reiser [this message]
2002-11-04 18:14 ` 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=3DC47735.9060206@namesys.com \
--to=reiser@namesys.com \
--cc=Nikita@namesys.com \
--cc=Reiserfs-Dev@namesys.com \
--cc=cliffw@osdl.org \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@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.