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 2C166D1B1B8 for ; Tue, 6 Jul 2004 13:50:48 -0300 (ADT) 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 47466-10 for ; Tue, 6 Jul 2004 16:50:47 +0000 (GMT) Received: from anubis.cinterfor.org.uy (r200-40-147-2.adinet.com.uy [200.40.147.2]) by svr1.postgresql.org (Postfix) with ESMTP id 12586D1B1AB for ; Tue, 6 Jul 2004 13:50:38 -0300 (ADT) Received: from cinterfor.org.uy (it01.cinterfor.org.uy [200.40.147.47]) by anubis.cinterfor.org.uy (8.11.6/8.11.2) with ESMTP id i66GTEo11350; Tue, 6 Jul 2004 13:29:15 -0300 Message-ID: <40EAD6A2.9030400@cinterfor.org.uy> Date: Tue, 06 Jul 2004 13:43:14 -0300 From: Rodrigo Filgueira Organization: CINTERFOR/OIT User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: es, en MIME-Version: 1.0 To: Frank Hsueh Cc: pgsql-performance@postgresql.org Subject: Re: to fsync or not to fsync (ext3?) References: <40EABDEF.3090607@cinterfor.org.uy> <753644204070608452ac91892@mail.gmail.com> In-Reply-To: <753644204070608452ac91892@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Cfor-MailScanner: Found to be clean/Hallado libre de virus X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.2 tagged_above=0.0 required=5.0 tests=NORMAL_HTTP_TO_IP X-Spam-Level: X-Archive-Number: 200407/16 X-Sequence-Number: 7407 Frank, thanks for your answer, This article http://www.linuxjournal.com/print.php?sid=5841 evaluates performance from a relational database point of view and it concludes that ext3 is faster. The articles you provided evaluate filesystems by using basic shell commands, copy, tar, touch. I really don't know why ext3 would be faster for databases but here are some tests that suggest this is true, I run pgbench with data=writeback for ext3, this is as ext2 as an ext3 fs can get, and results are more or less the same as with data=journal Best run with data=journal ------------------------------------ [root@dbs pgbench]# ./pgbench -U dba -P 4ghinec osdb -c 10 -s 11 -t 1000 starting vacuum...end. transaction type: TPC-B (sort of) scaling factor: 1 number of clients: 10 number of transactions per client: 1000 number of transactions actually processed: 10000/10000 tps = 349.844978 (including connections establishing) tps = 350.715286 (excluding connections establishing) Best run with data=writeback ---------------------------------------- [root@dbs pgbench]# ./pgbench -U dba -P 4ghinec osdb -c 10 -s 11 -t 1000 starting vacuum...end. transaction type: TPC-B (sort of) scaling factor: 1 number of clients: 10 number of transactions per client: 1000 number of transactions actually processed: 10000/10000 tps = 319.239210 (including connections establishing) tps = 319.961564 (excluding connections establishing) anybody else can throw some light on this? Frank Hsueh wrote: >Rodrigo, > > >>Hello there, I'm trying to make sure my postgres 7.4 is running as fast >>as it can in my box. >> >> >>My Software config is: >> >>RedHat 7.3 - 2.4.20-28.7smp Kernel, reporting four processors because of >>hyper threading. >>Postgres 7.4 >>Data directory is on a ext3 journaled filesystem (data=journal) >> >> >Isn't ext3 a really slow journaled filesystem [1, 2] to begin with? > >[1] http://slashdot.org/article.pl?sid=04/05/11/134214 >[2] http://209.81.41.149/~jpiszcz/index.html > >It might be a good experiment to figure out how different file systems >affect perf. > > Rodrigo Filgueira Prates IT@CINTERFOR/OIT http://www.cinterfor.org.uy