X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A5DA43A5F41 for ; Thu, 13 Jan 2005 05:09:26 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 47967-01 for ; Thu, 13 Jan 2005 05:09:15 +0000 (GMT) Received: from floppy.pyrenet.fr (news.pyrenet.fr [194.250.190.2]) by svr1.postgresql.org (Postfix) with ESMTP id 66FC83A5EFB for ; Thu, 13 Jan 2005 05:09:15 +0000 (GMT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 677FB31960; Thu, 13 Jan 2005 06:09:14 +0100 (MET) From: "Pete de Zwart" X-Newsgroups: pgsql.performance References: <41e39b04$0$96857$c30e37c6@ken-reader.news.telstra.net> Subject: Re: Best filesystem for PostgreSQL Database Cluster under Linux Date: Wed, 12 Jan 2005 07:25:43 +1100 Organization: Froob Networks X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-RFC2646: Format=Flowed; Original Lines: 47 Message-ID: <41e4364a$0$96874$c30e37c6@ken-reader.news.telstra.net> To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.336 tagged_above=0 required=5 tests=AWL, DATE_IN_PAST_24_48, PRIORITY_NO_NAME X-Spam-Level: * X-Archive-Number: 200501/179 X-Sequence-Number: 9869 Thanks for the info. I managed to pull out some archived posts to this list from the PostgreSQL web site about this issue which have helped a bit. Unfortunatly, the FS has been chosen before considering the impact of it on I/O for PostgreSQL. As the Cluster is sitting on it's on 200GB IDE drive for the moment and the system is partially live, it's not feasable to change the underlying file system without great pain and suffering. In the great fsync debates that I've seen, the pervasive opinion about journalling file systems under Linux and PostgreSQL is to have the filesystem mount option data=writeback, assuming that fsync in PostgreSQL will handle coherency of the file data and the FS will handle metadata. This is all academic to a point, as tuning the FS will get a small improvement on I/O compared to the improvement potential of moving to SCSI/FCAL, that and getting more memory. Regards, Pete de Zwart. "Christopher Browne" wrote in message news:m3zmzgayzl.fsf@knuth.knuth.cbbrowne.com... > Your understanding of the impact of filesystem journalling isn't > entirely correct. In the cases of interest, journalling is done on > metadata, not on the contents of files, with the result that there > isn't really that much overlap between the two forms of "journalling" > that are taking place. > > I did some benchmarking last year that compared, on a write-heavy > load, ext3, XFS, and JFS. > > I found that ext3 was materially (if memory serves, 15%) slower than > the others, and that there was a persistent _slight_ (a couple > percent) advantage to JFS over XFS. > > This _isn't_ highly material, particularly considering that I was > working with a 100% Write load, whereas "real world" work is likely to > have more of a mixture. > > If you have reason to consider one filesystem or another better > supported by your distribution vendor, THAT is a much more important > reason to pick a particular filesystem than 'raw speed.'