From: Hans Reiser <reiser@namesys.com>
To: Ron Joffe <rjoffe@yahoo.com>
Cc: reiserfs-list@namesys.com
Subject: status of reiser4
Date: Tue, 25 Oct 2005 15:23:03 -0700 [thread overview]
Message-ID: <435EB047.1040001@namesys.com> (raw)
In-Reply-To: <200510251658.48802.rjoffe@yahoo.com>
Ron Joffe wrote:
>On Tuesday 25 October 2005 14:13, Hans Reiser wrote:
>
>
>>If yes, what steps did you take to do it?
>>
>>
>
>Not quite there yet, but would like to test it out.
>
>Hans, could you give a status of Reiser4. I have seen allot of different
>issues on the maillist, but not a "status" of where the overall project
>stands.
>
>Thanks,
>
>Ron
>
>
>
vs is working on a major update that he will release any day now. It
contains many bug fixes. It should deturkey our latest reiser4 release,
sorry about that guys.
Nate did a mongo benchmark on an older reiser4, -mm1 or some such, and
the surprising thing we discovered was that reiser4 is now more cpu
efficient than ext3 for mongo. I guess all those memory copy avoiding
balancing algorithms that made the code so hairy and added so much to
the coding time are now paying off.;-) We should do some detailed
profiling, and careful benchmark comparisons over time, and see if
memory copies are now the big remaining hogs and reiser4 is being more
space efficient in RAM thus going faster, or if ext3 is just doing
something wasteful.
We should do fresh benchmarks on the latest reiser4 also.
next prev parent reply other threads:[~2005-10-25 22:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 18:13 has anyone installed SuSE 10.0 on reiser4? Hans Reiser
2005-10-25 20:58 ` Ron Joffe
2005-10-25 21:50 ` David Masover
2005-10-25 22:24 ` Hans Reiser
2005-10-25 22:23 ` Hans Reiser [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-17 18:18 status of reiser4 Hans Reiser
2004-12-17 18:54 ` Jake Maciejewski
2004-12-18 10:26 ` Vladimir Saveliev
2004-12-18 21:22 ` maciejej
2004-12-20 5:48 ` mjt
2004-12-27 12:38 ` Sander
2004-12-18 9:58 ` Maciej Soltysiak
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=435EB047.1040001@namesys.com \
--to=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=rjoffe@yahoo.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.