From: Chris Mason <mason@suse.com>
To: Bruce Guenter <lists-reiserfs-list@bruce-guenter.dyndns.org>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiserfs concurrent write problems
Date: Mon, 26 Apr 2004 13:36:11 -0400 [thread overview]
Message-ID: <1083000970.30344.50.camel@watt.suse.com> (raw)
In-Reply-To: <20040426172648.GA22918@em.ca>
On Mon, 2004-04-26 at 13:26, Bruce Guenter wrote:
> Greetings.
>
> I have been running a series of custom benchmarks to see what
> filesystems perform best for a maildir-based mail server.
>
> http://untroubled.org/benchmarking/2004-04/
>
> So far, reiserfs has by far the best reading rate, but has serious
> problems when more than one writer is trying to fsync concurrently.
> Also, adding an external journal actually slows down the procedure
> instead of improving performance. Are there any configuration changes
> or patches I should be trying to improve write performance?
Please try 2.6.6-rc2-mm2, which has new block allocator patches and
other speedups.
The default mount options should work best for you, but this might work
too:
mount -o alloc=skip_busy:dirid_groups /dev/xxx /mnt
Depending on the file size,
mount -o notail can make a huge difference too.
-chris
next prev parent reply other threads:[~2004-04-26 17:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 17:26 Reiserfs concurrent write problems Bruce Guenter
2004-04-26 17:36 ` Chris Mason [this message]
2004-04-26 18:12 ` Bruce Guenter
2004-04-27 16:15 ` Bruce Guenter
2004-04-27 18:00 ` Chris Mason
2004-04-27 20:15 ` Bruce Guenter
2004-04-27 23:48 ` Chris Mason
2004-04-28 23:48 ` Chris Mason
2004-04-29 19:04 ` Bruce Guenter
2004-04-29 19:19 ` Chris Mason
2004-04-29 20:08 ` Bruce Guenter
2004-04-29 20:16 ` Chris Mason
2004-04-30 19:54 ` Bruce Guenter
2004-04-30 20:24 ` Chris Mason
2004-04-30 21:44 ` Bruce Guenter
2004-05-01 14:52 ` Dieter Nützel
2004-05-01 9:26 ` Paul Wagland
2004-05-01 12:16 ` Chris Mason
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=1083000970.30344.50.camel@watt.suse.com \
--to=mason@suse.com \
--cc=lists-reiserfs-list@bruce-guenter.dyndns.org \
--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.