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 A816C3A3F22 for ; Mon, 8 Nov 2004 15:14:20 +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 07960-09 for ; Mon, 8 Nov 2004 15:14:11 +0000 (GMT) Received: from neptune.lgu.ac.uk (neptune.lgu.ac.uk [140.97.30.6]) by svr1.postgresql.org (Postfix) with ESMTP id B80133A3F0C for ; Mon, 8 Nov 2004 15:14:13 +0000 (GMT) Received: from solent (cal42-234.lgu.ac.uk [140.97.42.234]) by neptune.lgu.ac.uk (8.12.10/8.12.10) with ESMTP id iA8FDkO6000515; Mon, 8 Nov 2004 15:13:46 GMT Reply-To: From: "Matt Clark" To: "'Dawid Kuroczko'" , Subject: Re: ext3 journalling type Date: Mon, 8 Nov 2004 15:14:04 -0000 Organization: Ymogen Ltd Message-ID: <000d01c4c5a5$96202020$8300a8c0@solent> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal In-Reply-To: <758d5e7f04110804263efdf475@mail.gmail.com> X-LGU-MailScanner: Found to be clean X-MailScanner-From: matt@ymogen.net X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/141 X-Sequence-Number: 9095 > Am I right to assume that "writeback" is both fastest and at=20 > the same time as safe to use as ordered? Maybe any of you=20 > did some benchmarks? It should be fastest because it is the least overhead, and safe because postgres does it's own write-order guaranteeing through fsync(). You = should also mount the FS with the 'noatime' option. But.... For some workloads, there are tests showing that = 'data=3Djournal' can be the fastest! This is because although the data is written twice = (once to the journal, and then to its real location on disk) in this mode data is written _sequentially_ to the journal, and later written out to its destination, which may be at a quieter time. There's a discussion (based around 7.2) here: http://www.kerneltraffic.org/kernel-traffic/kt20020401_160.txt M