From: David Rees <drees76@gmail.com>
To: david@lang.hm
Cc: Dave Cramer <pg@fastcrypt.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: I have a fusion IO drive available for testing
Date: Fri, 27 Mar 2009 13:33:18 -0700
Message-ID: <72dbd3150903271333pfd63105i8076bf26858eaee1@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0903271026590.20251@asgard.lang.hm>
References: <491f66a50903260547p552f6d86kc51f8988898c19e4@mail.gmail.com>
<alpine.DEB.1.10.0903271026590.20251@asgard.lang.hm>
On Fri, Mar 27, 2009 at 10:30 AM, <david@lang.hm> wrote:
> On Thu, 26 Mar 2009, Dave Cramer wrote:
>> So far using dd I am seeing around 264MB/s on ext3, 335MB/s on ext2 write
>> speed. So the question becomes what is the best filesystem for this drive?
>
> until the current mess with ext3 and fsync gets resolved, i would say it
> would probably be a bad choice. I consider ext4 too new, so I would say XFS
> or ext2 (depending on if you need the journal or not)
If you're worried about the performance implications of ext3 in
data=ordered mode, the best thing to do is to mount the filesystem in
data=writeback mode instead.
If you're only using the filesystem for PostgreSQL data or logs, your
data will be just as safe except now that data and metadata won't be
forced to disk in the order it was written.
And you still get the benefit of a journal so fsck's after a crash will be fast.
XFS probably is a decent choice, but I don't have much experience with
it except on a desktop system where I can tell you that having write
barriers on absolutely kills performance of anything that does a lot
of filesystem metadata updates. Again, not a big concern if the
filesystem is only being used for PostgreSQL data or logs.
-Dave
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: drees76@gmail.com, david@lang.hm, pg@fastcrypt.com
Subject: Re: I have a fusion IO drive available for testing
In-Reply-To: <72dbd3150903271333pfd63105i8076bf26858eaee1@mail.gmail.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