From: Edward Shishkin <edward@namesys.com>
To: sander@humilis.net, Larry McVoy <lm@bitmover.com>
Cc: linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: reiserfs for bkbits.net?
Date: Wed, 11 Feb 2004 19:44:23 +0300 [thread overview]
Message-ID: <402A5BE7.583D9D68@namesys.com> (raw)
In-Reply-To: 20040211161358.GA11564@favonius
Sander wrote:
>
> Larry McVoy wrote (ao):
> > We're moving openlogging back to our offices and I'm experimenting
> > with filesystems to see what gives the best performance for BK usage.
> > Reiserfs looks pretty good and I'm wondering if anyone knows any
> > reasons that we shouldn't use it for bkbits.net. Also, would it help
> > if the journal was on a different disk?
Not much if you mean performance: here is results for standard journal vs
journal relocated to NVRAM, everything in data logging journal mode:
http://thebsh.namesys.com/benchmarks/journal_relocation_to_NVRAM.html
Edward.
Most of the bkbits traffic is
> > read so I doubt it.
> >
> > Please cc me, I'm not on the list.
>
> I've cc'ed the Reiserfs mailinglist.
>
> IME Reiserfs is a fast and stable fs. If you have the time to benchmark
> ext3, reiserfs, jfs and xfs (and ..) with bk then you would know first
> hand which fs is best for you. It might be worth the time.
>
> With kind regards, Sander
>
> --
> Humilis IT Services and Solutions
> http://www.humilis.net
next prev parent reply other threads:[~2004-02-11 16:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 15:23 reiserfs for bkbits.net? Larry McVoy
2004-02-11 16:13 ` Sander
2004-02-11 16:18 ` Nikita Danilov
2004-02-11 16:30 ` Måns Rullgård
2004-02-11 18:29 ` Bryan Whitehead
2004-02-11 18:55 ` Måns Rullgård
2004-02-11 19:19 ` Larry McVoy
2004-02-12 1:06 ` Hans Reiser
2004-02-14 5:54 ` Larry McVoy
2004-02-12 8:47 ` Mihai RUSU
2004-02-11 16:44 ` Edward Shishkin [this message]
2004-02-11 16:53 ` Mihai RUSU
2004-02-11 18:05 ` Larry McVoy
2004-02-11 18:41 ` Erik Hensema
2004-02-12 13:40 ` Tomas Szepe
2004-02-19 22:33 ` Pavel Machek
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=402A5BE7.583D9D68@namesys.com \
--to=edward@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=reiserfs-list@namesys.com \
--cc=sander@humilis.net \
/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