From: Hans Reiser <reiser@namesys.com>
To: Dirk Mueller <dmuell@gmx.net>
Cc: Chris Mason <mason@suse.com>,
reiserfs-list@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-list] ReiserFS seems to be stable as of 2.4.4
Date: Sun, 06 May 2001 17:19:16 -0700 [thread overview]
Message-ID: <3AF5EA03.5D92B2E6@namesys.com> (raw)
In-Reply-To: <20010504182357.A20214@rotes20.wohnheim.uni-kl.de> <341650000.988994279@tiny> <20010504192348.A11507@rotes20.wohnheim.uni-kl.de>
Dirk Mueller wrote:
>
> Now consider a good amount of fragmentation because those files get created
> over time (weeks, months etc). and you quickly degenerade to a scanning
> speed of maybe 10-20 files per second (Athlon 800, IBM 60GB HD with roughly
> 35MB/s linear read). It was that horrible that I quickly returned to mbox
> for those lists with high amount of traffic.
I think only a repacker can properly cure performance problems of slowly
accumulating files and directories . September 2002.
We can do other things that will gain 5 percent here and there, but the repacker
will be the real cure.
Hans
parent reply other threads:[~2001-05-06 22:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20010504192348.A11507@rotes20.wohnheim.uni-kl.de>]
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=3AF5EA03.5D92B2E6@namesys.com \
--to=reiser@namesys.com \
--cc=dmuell@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox