Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id E3F73634406 for ; Tue, 31 Mar 2009 09:26:06 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 97627-01 for ; Tue, 31 Mar 2009 09:25:57 -0300 (ADT) X-Greylist: delayed 00:05:19.601362 by SQLgrey-1.7.6 Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by mail.postgresql.org (Postfix) with ESMTP id 3862F633D50 for ; Tue, 31 Mar 2009 09:26:04 -0300 (ADT) Received: by qw-out-2122.google.com with SMTP id 8so1721819qwh.61 for ; Tue, 31 Mar 2009 05:26:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=7NCNlZb1bYbmHlk8ki12dbaBgpmZlsycJxrEGrsXOKo=; b=wR0/jz8dKOuj/FstHlMevtto06Domwsek0DbVYO7tZSEVrzvm3iw/qD2xQKopwCsm+ f/fa+MLIqUPiW4vQlTuG6M5TEA7ZQSFCALmb/NWq/garByNKyVi3Dodf7nBbMCr710gw zbkD0ZuSjneIO9F1RfBmtRHVRKn/hO57yykSs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=UvM+L1wSxOIF4+dOMEmyJDj3wO5IqzXcX3KWnvdvURPhNLhmosVRmsqwAUraNFBXZA WvBm2RG0mn7r1GeG6oov3e35SrqDi4rUhhVXnaRDjY46MEnB/WY49qQ9ZD9trBSdp/Hf 8UM3m/3+GdngjkAHnP+c0RI/764na9RwfXo/4= MIME-Version: 1.0 Received: by 10.229.82.9 with SMTP id z9mr2261960qck.79.1238502041489; Tue, 31 Mar 2009 05:20:41 -0700 (PDT) In-Reply-To: <72dbd3150903271333pfd63105i8076bf26858eaee1@mail.gmail.com> References: <491f66a50903260547p552f6d86kc51f8988898c19e4@mail.gmail.com> <72dbd3150903271333pfd63105i8076bf26858eaee1@mail.gmail.com> Date: Tue, 31 Mar 2009 08:20:41 -0400 X-Google-Sender-Auth: ee44355b1cd03a3d Message-ID: <491f66a50903310520j2d540fa9q3c0f8403bad60c14@mail.gmail.com> Subject: Re: I have a fusion IO drive available for testing From: Dave Cramer To: David Rees Cc: david@lang.hm, pgsql-performance@postgresql.org Content-Type: multipart/alternative; boundary=00163646d0c23c93970466693aa7 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200903/437 X-Sequence-Number: 33359 --00163646d0c23c93970466693aa7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On Fri, Mar 27, 2009 at 4:33 PM, David Rees wrote: > On Fri, Mar 27, 2009 at 10:30 AM, 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 > So I tried writing directly to the device, gets around 250MB/s, reads at around 500MB/s The client is using redhat so xfs is not an option. Dave --00163646d0c23c93970466693aa7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Fri, Mar 27, 2009 at 4:33 PM, David R= ees <drees76@gmai= l.com> wrote:
On Fri, Mar 27, 2009 at 10:30 AM, =A0<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 ext= 2 write
>> speed. So the question becomes what is the best filesystem for thi= s 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 sa= y XFS
> or ext2 (depending on if you need the journal or not)

If you're worried about the performance implications of ext3 in data=3Dordered mode, the best thing to do is to mount the filesystem in
data=3Dwriteback 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<= br> 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. =A0Again, not a big concern if the
filesystem is only being used for PostgreSQL data or logs.

-Dave

So I tried writing directly to the device, gets arou= nd 250MB/s, reads at around 500MB/s

The client is using redhat so xf= s is not an option.

Dave
--00163646d0c23c93970466693aa7--