From: Oleg Drokin <green@namesys.com>
To: Newsmail <newsmail@satimex.tvnet.hu>
Cc: reiserfs-list@namesys.com
Subject: Re: [BK] ReiserFS file write bug fix for 2.4
Date: Fri, 13 Sep 2002 09:05:40 +0400 [thread overview]
Message-ID: <20020913090540.A4723@namesys.com> (raw)
In-Reply-To: <5.1.1.6.2.20020912183504.01d24f60@pop.tvnet.hu>
Hello!
On Thu, Sep 12, 2002 at 06:40:10PM +0100, Newsmail wrote:
> > The mount option (-o alloc=prealloc min=4:preallocsize=9) only or better
> > a "reformat"?
> > Those mount options are no longer needed starting from 2.4.20-pre6.
> > They are default. Reformat is not needed, but all the blocks allocated by
> > old allocator will remain at their old places of course.
> I use 2.4.20-pre4 without these mount options. So apparently reiserfs is
> much slower than the optimal am I right? (if my memory is good this is
> about some speed optimization right?).
It depends on kind of workloads you have. But in general - yes, it is somewhat
slower and if you have massive parallel writers, on-disk blocks layout is
suboptimal.
You should use above mount options (alloc=preallocmin=4:preallocsize=9)
or upgrade to 2.4.19-pre7 (of that's not our yet, then to whatever is the
current state of Marcelo's bk repository is ).
Bye,
Oleg
next prev parent reply other threads:[~2002-09-13 5:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 17:40 [BK] ReiserFS file write bug fix for 2.4 Newsmail
2002-09-13 5:05 ` Oleg Drokin [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-11 17:04 Hans Reiser
2002-09-11 17:34 ` Dieter Nützel
2002-09-11 17:53 ` Oleg Drokin
2002-09-11 19:37 ` Dieter Nützel
2002-09-12 4:53 ` Oleg Drokin
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=20020913090540.A4723@namesys.com \
--to=green@namesys.com \
--cc=newsmail@satimex.tvnet.hu \
--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.