X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.192]) by svr1.postgresql.org (Postfix) with ESMTP id 7EEF7D1C4CC for ; Mon, 21 Jul 2003 10:30:02 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr4.postgresql.org [64.117.224.192]) (amavisd-new, port 10024) with ESMTP id 65044-09 for ; Mon, 21 Jul 2003 10:29:57 +0000 (GMT) Received: from smtp.pspl.co.in (unknown [202.54.11.65]) by svr1.postgresql.org (Postfix) with ESMTP id 3C199D1C4C9 for ; Mon, 21 Jul 2003 07:29:56 -0300 (ADT) Received: (from root@localhost) by smtp.pspl.co.in (8.12.9/8.12.9) id h6LAZ4HF027230 for ; Mon, 21 Jul 2003 16:05:04 +0530 Received: from daithan (daithan.intranet.pspl.co.in [192.168.7.161]) (authenticated bits=0) by smtp.pspl.co.in (8.12.9/8.12.9) with ESMTP id h6LAZ46O027217 for ; Mon, 21 Jul 2003 16:05:04 +0530 From: "Shridhar Daithankar" To: pgsql-performance@postgresql.org Date: Mon, 21 Jul 2003 16:01:41 +0530 MIME-Version: 1.0 Subject: Re: Tuning PostgreSQL Reply-To: shridhar_daithankar@persistent.co.in Message-ID: <3F1C0E65.27609.14A7BA43@localhost> In-reply-to: <3F1BBBD3.6070405@bytecraft.com.my> References: <3F1C00B2.20319.147235A4@localhost> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/326 X-Sequence-Number: 2619 On 21 Jul 2003 at 18:09, Ang Chin Han wrote: > Shridhar Daithankar wrote: > > On 21 Jul 2003 at 11:23, Alexander Priem wrote: > > >>I use ext3 filesystem, which probably is not the best performer, is it? > > > > No. You also need to check ext2, reiser and XFS. There is no agreement between > > users as in what works best. You need to benchmark and decide. > > Need? Maybe I'm a bit disillusioned, but are the performances between > the filesystems differ so much as to warrant the additional effort? > (e.g. XFS doesn't come with Red Hat 9 -- you'll have to patch the > source, and compile it yourself). Well, the benchmarking is not to prove which filesystem is fastest and feature rich but to find out which one suits your needs best. > Benchmarking it properly before deployment is tough: are the test load > on the db/fs representative of actual load? Is 0.5% reduction in CPU > usage worth it? Did you test for catastrophic failure by pulling the > plug during write operations (ext2) to test if the fs can handle it? Is > the code base for the particular fs stable enough? Obscure bugs in the fs? Well, that is what that 'benchmark' is supposed to find out. Call it pre- deployment testing or whatever other fancy name one sees fit. But it is a must in almost all serious usage. > For the record, we tried several filesystems, but stuck with 2.4.9's > ext3 (Red Hat Advanced Server). Didn't hit a load high enough for the > filesystem choices to matter after all. :( Good for you. You have time at hand to find out which one suits you best. Do the testing before you have load that needs another FS..:-) Bye Shridhar -- It would be illogical to assume that all conditions remain stable. -- Spock, "The Enterprise" Incident", stardate 5027.3