From: Hans Reiser <reiser@namesys.com>
To: Fred -- Speed Up -- <speedup@free.fr>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiser4 bitmap & replication handling
Date: Tue, 20 May 2003 23:54:09 +0400 [thread overview]
Message-ID: <3ECA87E1.7070906@namesys.com> (raw)
In-Reply-To: <002d01c31efe$5da8b5d0$b300a8c0@xpstation>
Fred -- Speed Up -- wrote:
>I just read this article about XFS :
>http://www-106.ibm.com/developerworks/library/l-fs9.html
>
>It says XFS uses B+Trees as Reiser4 does, and it uses this structure to store not only the keys, but also the bitmap data and replicates it storage trees to improve scalability and overall wide-disk performance. It also tries to allocate the largest contigous blocks to a file (but Reiser4 does this also), and comes close to raw performance when reading large files. The article concludes XFS is faster than Reiser
>
well, his words are not quite that strong, and who knows if he is using
the latest journaling patches but XFS is a very nice filesystem.....
>(3.6 I think, as the article has been published in 2002 by Gentoo CEO Daniel Robbins) with performance tweaks at mount time.
>
Which he does not define, so we cannot reproduce it.
> But how does Reiser4 ?
>
>
Well, Reiser4 has much fewer seeks than other filesystems usually. The
current weakness of Reiser4 is CPU consumption, but our team is cutting
that down at great speed. It seems like each team member manages to
reduce it by >10% a week, and there are 3 of them working actively on
that. This is fortunate, because it is still very high..... I have
this fond hope that performance will be something very nice by
LinuxTag.....;-)
>How many times does Reiser replicate
>
what do you mean, replicate the tree?
>and/or truncate its tree, and what structure has been chosen for bitmap data ?
>
bitmaps.;-) we have some nice little tweaks, like we count the number of
used bits in every bitmap block so that we don't have to scan full
blocks, and we hash around if we scan too much, but I have to say that
bitmaps are nice and simple and work without a lot of code.
>Does Reiser4 divide the disk space in chunks, as XFS and ext2 do ?
>
No. We experimented a little bit with that, and didn't get clear
advantages. My mind is still open though if someone shows me something
compelling.
>Are you implementing some special features for very large disks,
>
how are they different
> RAID systems
>
Reiser4 will happen to work very well for them without understanding
them (not entirely a coincidence). I have as yet to get someone to fund
tuning for them specifically, though it would probably yield benefits to
do so.
> and multi-processing hardware
>
Reiser4 made a massive code investment into fine-grained locking.
>Is the developement far enough to get an idea of the final performance ?
>
Reiser4 inconsistently performs very very fast. We have no doubt that
we can make that consistent but it is a lot of measuring and tweaking
and measuring and tweaking.....
>I didn't remember, when do you plan to release Reiser4 ?
>
LinuxTag, July 11, if lucky, we will start our beta.
>
>I'm very interested in those brand new filesystem techniques, for now I think we can consider that XFS and Reiser3 are very close in overall performance. You're saying in the doc you'd like to keep on offering the best performance in the market : are you really that far ?
>
>Fred
>
>
--
Hans
next prev parent reply other threads:[~2003-05-20 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 18:33 Reiser4 bitmap & replication handling Fred -- Speed Up --
2003-05-20 19:54 ` Hans Reiser [this message]
[not found] ` <001701c31fb4$69e14090$b300a8c0@xpstation>
[not found] ` <3ECBE935.3000401@namesys.com>
2003-05-22 17:17 ` Fred -- Speed Up --
2003-05-23 7:33 ` Oleg Drokin
-- strict thread matches above, loose matches on Subject: below --
2003-05-22 16:14 Fred -- Speed Up --
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=3ECA87E1.7070906@namesys.com \
--to=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=speedup@free.fr \
/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.