From: Chris Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: XFS filessystem for Datawarehousing
Date: Wed, 02 Aug 2006 18:43:38 -0400
Message-ID: <603bcekbc5.fsf@dba2.int.libertyrms.com> (raw)
References: <C0F55F2D.2B856%llonergan@greenplum.com>
<01cb01c6b676$8ef67330$0a00a8c0@trivadis.com>
makulev@gmx.net ("Milen Kulev") writes:
> I am pretty exited whether XFS will clearly outpertform ETX3 (no
> default setups for both are planned !). I am not sure whether is it
> worth to include JFS in comparison too ...
I did some benchmarking about 2 years ago, and found that JFS was a
few percent faster than XFS which was a few percent faster than ext3,
on a "huge amounts of writes" workload.
That the difference was only a few percent made us draw the conclusion
that FS performance was fairly much irrelevant. It is of *vastly*
more importance whether the filesystem will survive power outages and
the like, and, actually, Linux hasn't fared as well with that as I'd
like. :-(
The differences are small enough that what you should *actually* test
for is NOT PERFORMANCE.
You should instead test for reliability.
- Turn off the power when the DB is under load, and see how well it
survives.
- Pull the fibrechannel cable, and see if the filesystem (and
database) survives when under load.
If you find that XFS is 4% faster, that's likely a *terrible*
trade-off if it only survives power outage half as often as (say)
ext3.
--
(reverse (concatenate 'string "gro.gultn" "@" "enworbbc"))
http://cbbrowne.com/info/wp.html
"C combines the power of assembler language with the convenience of
assembler language." -- Unknown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: cbbrowne@acm.org
Subject: Re: XFS filessystem for Datawarehousing
In-Reply-To: <603bcekbc5.fsf@dba2.int.libertyrms.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox