From: John Dong <john.dong@gmail.com>
To: reiserfs-list@namesys.com
Subject: Re: improving Reiserfs Performance
Date: Wed, 25 May 2005 20:36:23 -0400 [thread overview]
Message-ID: <cfec5fb8050525173623d33018@mail.gmail.com> (raw)
In-Reply-To: <42949FDF.8000406@darthvader.us>
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
>
>
> ReiserFS actually performs the best under heavy hammering and thousands
> of files IMHO ;)
One exception: In periods of extremely heavy read activity, writes do get
choked. And also vice versa. I can strongly feel this when doing some major
dd'ing, which probably won't simulate your load at all. The deadline I/O
scheduler did help out, though, for some reason. (my imagination?)
> Reiser4: again IMHO not yet, although your site would make a nice test
> bed :)
I agree with this statement. I ran reiser4 on 2 of my system. In the
2.6.8days, one reiser4 volume unexpectedly started exhibiting random
hangs. fsck
didn't find anything, and the hangs were VERY hard to reproduce, if at all.
(sometimes APT's building dependencies tree would spark it, but it's like a
.1% chance). The other one, reiser4's working fine
(2.6.11.10<http://2.6.11.10>),
but I really miss xattr (Beagle). Oh well, can't have everything.
[-- Attachment #2: Type: text/html, Size: 1278 bytes --]
prev parent reply other threads:[~2005-05-26 0:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 12:54 improving Reiserfs Performance Jos Houtman
[not found] ` <4294783C.5040001@darthvader.us>
[not found] ` <42947BCA.9080702@hyves.nl>
2005-05-25 15:55 ` Yiannis Mavroukakis
2005-05-25 16:24 ` Jos Houtman
2005-05-25 17:22 ` ReiserFS on large-scale flash Artem B. Bityuckiy
2005-05-25 17:31 ` Hans Reiser
2005-05-25 17:33 ` Artem B. Bityuckiy
2005-05-26 0:36 ` John Dong [this message]
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=cfec5fb8050525173623d33018@mail.gmail.com \
--to=john.dong@gmail.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.