Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id A1BEB634C42 for ; Tue, 24 Mar 2009 23:04:48 -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 89389-04 for ; Tue, 24 Mar 2009 23:04:35 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.171]) by mail.postgresql.org (Postfix) with ESMTP id 556406348F4 for ; Tue, 24 Mar 2009 23:04:44 -0300 (ADT) Received: by wf-out-1314.google.com with SMTP id 29so3572048wff.28 for ; Tue, 24 Mar 2009 19:04:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5eQIhbaOrEYLRBp5mDg0uyfNXvPyAlqQyvt95RSLfXQ=; b=QGEcWAbgZtAAiRDm6H5OBaEAnQFFy/DTIE0b6aBnIOx5B1WwifEBSR8CStO5lgLSL5 /AsKbpfX2oFvqV3kQf2srgdHPQEHHF2R4Tt5qTvpFO6s8DmdkXThyUn48UNHOKHTjYkU vj7ntTVDSaFka9b0YOIKt8iv0se/TQqY/lMfo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=iJ4EZPMNfPxD97mZjHTWncZRnQE2kUGOCe36kgjtDHqFUEZiII7kI7HZi1vcErc4Xd lT5mt4ucKm1D2vvB1wbpO4fxUhAAeyUxAR2zVSwdMIywattOCHxLXejvL03Tg1u0avyJ aF3ai2kR8ZT8t3kq1r70HcB00XBWEHN6CE1eY= MIME-Version: 1.0 Received: by 10.142.230.11 with SMTP id c11mr3667774wfh.246.1237946682565; Tue, 24 Mar 2009 19:04:42 -0700 (PDT) In-Reply-To: References: <49C98433.5080709@paradise.net.nz> Date: Tue, 24 Mar 2009 19:04:42 -0700 Message-ID: <72dbd3150903241904t39a2304cv806b228cbaef3036@mail.gmail.com> Subject: Re: Raid 10 chunksize From: David Rees To: Scott Carey Cc: Mark Kirkwood , "pgsql-performance@postgresql.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.25 tagged_above=0 required=5 tests=AWL=2.250 X-Spam-Level: ** X-Archive-Number: 200903/356 X-Sequence-Number: 33278 On Tue, Mar 24, 2009 at 6:48 PM, Scott Carey wrot= e: > Your xlogs are occasionally close to max usage too -- which is suspicious= at > 10MB/sec. =A0There is no reason for them to be on ext3 since they are a > transaction log that syncs writes so file system journaling doesn't mean > anything. =A0Ext2 there will lower the sync times and reduced i/o utiliza= tion. I would tend to recommend ext3 in data=3Dwriteback and make sure that it's mounted with noatime over using ext2 - for the sole reason that if the system shuts down unexpectedly, you don't have to worry about a long fsck when bringing it back up. Performance between the two filesystems should really be negligible for Postgres logging. -Dave