From: | Chris Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: XFS filessystem for Datawarehousing |
Date: | 2006-08-02 22:43:38 |
Message-ID: | 603bcekbc5.fsf@dba2.int.libertyrms.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
makulev(at)gmx(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Stone | 2006-08-02 23:33:39 | Re: XFS filessystem for Datawarehousing |
Previous Message | Milen Kulev | 2006-08-02 21:44:06 | Re: XFS filessystem for Datawarehousing |