Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 0BA936329C6 for ; Tue, 10 Nov 2009 11:29:53 -0400 (AST) 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 96074-05 for ; Tue, 10 Nov 2009 15:29:33 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ew0-f218.google.com (mail-ew0-f218.google.com [209.85.219.218]) by mail.postgresql.org (Postfix) with ESMTP id 7EA0D62E33C for ; Tue, 10 Nov 2009 11:29:35 -0400 (AST) Received: by ewy18 with SMTP id 18so135935ewy.19 for ; Tue, 10 Nov 2009 07:29:33 -0800 (PST) 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; bh=PQ7upEAhtBf2LRunB32xHPTTyyM2M7kj6aL9Jdvh8Cc=; b=JjjF5OCR++yIhW+TJZg8YfkXfm4kzEXtZlIUWs/jNQEvaBRrrNj+2w27+tdwAA8YZ7 Lzg2LRZbmbZrQWEZvjNPvbswFdtv3XwYl+5flmuBbbEXBfzc6dUsVCEilECoBUU/3DDQ UkubgTtDl+xpFszP3qcX/9GFKPNtFjZysUaLA= 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; b=INfSWwr175smo6MAdBDtU4f2AA8ZnvzNsiv8Uxjvrbbqevz3d3qhIai5bjCbdPl8A5 hJ1HnG7pkHJbVgQ03cOiETMU3TDDBqb7tAVfw7ZPchD6ya3O97mOFuEomdfw+BZGXhJ8 hphPDaGGZhVIIPqQ3oFWLUpN+WQ6KmTeZFOeE= MIME-Version: 1.0 Received: by 10.216.89.82 with SMTP id b60mr64950wef.170.1257866972880; Tue, 10 Nov 2009 07:29:32 -0800 (PST) In-Reply-To: References: <8a1bfe660911100355l34a557ffj8244079c1fb689b5@mail.gmail.com> <8a1bfe660911100700l2a44f638m97ea6136b65deb21@mail.gmail.com> Date: Tue, 10 Nov 2009 16:29:32 +0100 Message-ID: <8a1bfe660911100729q42ac732cga9bbadd52e2533dd@mail.gmail.com> Subject: Re: limiting performance impact of wal archiving. From: Laurent Laborde To: Ivan Voras Cc: pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 200911/101 X-Sequence-Number: 36269 On Tue, Nov 10, 2009 at 4:11 PM, Ivan Voras wrote: > Laurent Laborde wrote: > > Ok, this explains it. It also means you are probably not getting much > runtime performance benefits from the logging and should think about moving > the logs to different drive(s), among other things because... It is on a separate array which does everything but tablespace (on a separate array) and indexspace (another separate array). >> Of course, when doing sequential read it goes to +250MB/s :) > > ... it means you cannot dedicate 0.064 of second from the array to read > through a single log file without your other transactions suffering. Well, actually, i also change the configuration to synchronous_commit=off It probably was *THE* problem with checkpoint and archiving :) But adding cstream couldn't hurt performance, and i wanted to share this with the list. :) BTW, if you have any idea to improve IO performance, i'll happily read it. We're 100% IO bound. eg: historically, we use JFS with LVM on linux. from the good old time when IO wasn't a problem. i heard that ext3 is not better for postgresql. what else ? xfs ? *hugs* -- ker2x Sysadmin & DBA @ http://www.over-blog.com/