All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Guenter <lists-reiserfs-list@bruce-guenter.dyndns.org>
To: reiserfs-list@namesys.com
Subject: Reiserfs concurrent write problems
Date: Mon, 26 Apr 2004 11:26:48 -0600	[thread overview]
Message-ID: <20040426172648.GA22918@em.ca> (raw)

[-- Attachment #1: Type: text/plain, Size: 691 bytes --]

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?

Thanks.
-- 
Bruce Guenter <bruceg@em.ca> http://em.ca/~bruceg/ http://untroubled.org/
OpenPGP key: 699980E8 / D0B7 C8DD 365D A395 29DA  2E2A E96F B2DC 6999 80E8

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-04-26 17:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-26 17:26 Bruce Guenter [this message]
2004-04-26 17:36 ` Reiserfs concurrent write problems Chris Mason
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=20040426172648.GA22918@em.ca \
    --to=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.