All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fred -- Speed Up --" <speedup@free.fr>
To: reiserfs-list@namesys.com
Subject: Re: Reiser4 bitmap & replication handling
Date: Thu, 22 May 2003 19:17:45 +0200	[thread overview]
Message-ID: <006401c32086$105ea350$b300a8c0@xpstation> (raw)
In-Reply-To: 3ECBE935.3000401@namesys.com

Here are Hans's interesting answers to my previous post, thank you Hans ;)
Just a little question : when do you plan to update the kernel patch, which
is 3 month old ?

Fred

> >Maybe some really big files handling performance improvements, to near
XFS
> >performance in this domain. I'm not really concerned, but some specific
> >systems may need such features only offered by XFS. Do you plan to
release
> >different versions of the filesystem's plugins to adapt to different
systems
> >ans situations ?
>
> Large file performance is not really considered the hard thing in FS
> design (unless you do data journaling or atomicity, in which case we are
> twice as fast).

> >>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.....
> >Sorry but ... what do you mean by "unconsistently" ? Does this mean you
only
> >consider avarage performance, ignoring worse cases ?
>
> I mean we have lots of crud left to clean out of the code.  If you test
> it in a way that avoids the crud, we are fast, if you hit the crud we
> are slow.  Decrudding is in progress.;-)

> >Another question, do you want to release Reiser4 so that it will be
> >presented on LinuxTag because :
> >1- The developement team is mainly composed of german people
> >2- Suse will have a very big area on the show
> >3- The release date just accorded to the LinuxTag opening
> >4- All of you especially like LinuxTag :-D
>
> I like LinuxTag, and I am speaking there, and if we can release it then
> without rushing the code, it will be nice.  No promises, the code ships
> when the code is ready and not before....


  parent reply	other threads:[~2003-05-22 17:17 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
     [not found]   ` <001701c31fb4$69e14090$b300a8c0@xpstation>
     [not found]     ` <3ECBE935.3000401@namesys.com>
2003-05-22 17:17       ` Fred -- Speed Up -- [this message]
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='006401c32086$105ea350$b300a8c0@xpstation' \
    --to=speedup@free.fr \
    --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.