From: Hans Reiser <reiser@namesys.com>
To: "Markus Törnqvist" <mjt@nysv.org>
Cc: David Masover <ninja@slaphack.com>,
Pierre Etchemaite <petchema@concept-micro.com>,
reiserfs-list@namesys.com
Subject: Re: reiserfs3, rsync and hardlinks
Date: Tue, 08 Feb 2005 14:24:07 -0800 [thread overview]
Message-ID: <42093C07.4010804@namesys.com> (raw)
In-Reply-To: <20050208094257.GX26192@nysv.org>
Reiser4 CPU usage is reasonable now I think. If you experience that it
is too high, use the extents only mount option, and it should be pretty
good. Maybe somebody has some time to create some numbers? I could be
wrong, but let us look at numbers.....
Hans
Markus Törnqvist wrote:
>
>
>
>>Think I remember some other filesystem being really lightweight CPU.
>>UFS or something. But XFS shouldn't be too bad. Where does your
>>"probably" come from?
>>
>>
>
>UFS as in Unix File System? Eww..
>
>Dunno about CPU usage, but I tested XFS once and it was painfully slow.
>Fortunately it got better, so maybe my test was somewhat flawed.
>
>Maybe the Namesys guys would want to release some new and up-to-date
>benchmarks now that the AMD64 panic bug is fixed?
>
>
>
next prev parent reply other threads:[~2005-02-08 22:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 2:41 reiserfs3, rsync and hardlinks Pierre Etchemaite
2005-02-06 19:18 ` David Masover
2005-02-06 21:55 ` Pierre Etchemaite
2005-02-07 5:33 ` David Masover
2005-02-08 9:42 ` mjt
2005-02-08 22:24 ` Hans Reiser [this message]
2005-02-07 10:22 ` Vladimir Saveliev
2005-02-07 20:50 ` Pierre Etchemaite
2005-02-07 21:32 ` Chris Mason
2005-02-08 5:53 ` David Masover
2005-02-08 22:14 ` Hans Reiser
2005-02-09 8:28 ` Pierre Etchemaite
2005-02-08 11:16 ` Vladimir Saveliev
2005-02-09 8:22 ` Pierre Etchemaite
2005-02-07 19:26 ` Hans Reiser
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=42093C07.4010804@namesys.com \
--to=reiser@namesys.com \
--cc=mjt@nysv.org \
--cc=ninja@slaphack.com \
--cc=petchema@concept-micro.com \
--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.