From: Michael Tokarev <mjt@tls.msk.ru>
To: David Dougall <davidd@et.byu.edu>
Cc: Arshavir Grigorian <ag@m-cam.com>,
linux-raid@vger.kernel.org, pgsql-performance@postgresql.org
Subject: Re: Postgres on RAID5
Date: Wed, 16 Mar 2005 19:55:49 +0300 [thread overview]
Message-ID: <42386515.1070103@tls.msk.ru> (raw)
In-Reply-To: <Pine.LNX.4.58.0503160947080.11922@lewis.et.byu.edu>
David Dougall wrote:
> In my experience, if you are concerned about filesystem performance, don't
> use ext3. It is one of the slowest filesystems I have ever used
> especially for writes. I would suggest either reiserfs or xfs.
I'm a bit afraid to start yet another filesystem flamewar, but.
Please don't make such a claims without providing actual numbers
and config details. Pretty please.
ext3 performs well for databases, there's no reason for it to be
slow. Ok, enable data=journal and use it with eg Oracle - you will
see it is slow. But in that case it isn't the filesystem to blame,
it's operator error, simple as that.
And especially reiserfs, with its tail packing enabled by default,
is NOT suitable for databases...
/mjt
next prev parent reply other threads:[~2005-03-16 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 19:48 Postgres on RAID5 Arshavir Grigorian
2005-03-14 4:36 ` [PERFORM] " Greg Stark
2005-03-14 7:44 ` [PERFORM] Postgres on RAID5 (possible sync blocking read type issue on 2.6.11) David Greaves
2005-03-14 19:53 ` [PERFORM] Postgres on RAID5 Alex Turner
2005-03-14 20:17 ` Greg Stark
2005-03-14 20:35 ` Jim Buttafuoco
2005-03-14 21:03 ` Arshavir Grigorian
2005-03-14 22:47 ` Michael Tokarev
2005-03-14 23:49 ` Guy
2005-03-15 16:17 ` Effect of Stripe Size (was Postgres on RAID5) Ruth Ivimey-Cook
2005-03-16 16:47 ` Postgres on RAID5 David Dougall
2005-03-16 16:55 ` Michael Tokarev [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-11 21:18 Arshavir Grigorian
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=42386515.1070103@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=ag@m-cam.com \
--cc=davidd@et.byu.edu \
--cc=linux-raid@vger.kernel.org \
--cc=pgsql-performance@postgresql.org \
/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;
as well as URLs for NNTP newsgroup(s).