Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 7C0D9635111 for ; Tue, 10 Nov 2009 07:56:51 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 42974-03-4 for ; Tue, 10 Nov 2009 11:56:43 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ew0-f228.google.com (mail-ew0-f228.google.com [209.85.219.228]) by mail.postgresql.org (Postfix) with ESMTP id 9B36E634346 for ; Tue, 10 Nov 2009 07:55:46 -0400 (AST) Received: by ewy28 with SMTP id 28so5923518ewy.42 for ; Tue, 10 Nov 2009 03:55:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=cD7DvrNtebLZfi8Fy7DZK7qo2cPGNd3+WuJiAZuKlPY=; b=fchvSAzB3/g14tobOtkCjWKD32EWYr+CfKqxAXhB+9VmZJQaegGRZEYPvKniDPSEeM IM75PXHtNwzpuYLaE0+/OgGXfAHhUTxrCEMMMTm9xYxymc++yBp7VrmjxquHCrloot68 21vPNzpcitJuFKrqXH/XFwGUOQylUshMAkJiI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=mTK4LwA+BTaE0w5z8EVL3FLYCpeBbNA7f3CvVVuw9KYGzEI4HqS1lhY9YhGDBYnjw7 vOCA7HPLU+3F9xfEsSPAoz/Ok3vgPstS8xsJUnbS7llF0sGQx6Yio2EdKgyZN2BT9Azw qvo3nJF9xyCZo99NdE4LSHfB8b5DtNaa0I0mc= MIME-Version: 1.0 Received: by 10.216.89.194 with SMTP id c44mr2728112wef.199.1257854142110; Tue, 10 Nov 2009 03:55:42 -0800 (PST) Date: Tue, 10 Nov 2009 12:55:42 +0100 Message-ID: <8a1bfe660911100355l34a557ffj8244079c1fb689b5@mail.gmail.com> Subject: limiting performance impact of wal archiving. From: Laurent Laborde To: PostgreSQL Performance Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.11 tagged_above=-10 required=5 tests=BAYES_05=-1.11 X-Spam-Level: X-Archive-Number: 200911/96 X-Sequence-Number: 36264 Hi ! We recently had a problem with wal archiving badly impacting the performance of our postgresql master. And i discovered "cstream", that can limite the bandwidth of pipe stream. Here is our new archive command, FYI, that limit the IO bandwidth to 500KB/s : archive_command = '/bin/cat %p | cstream -i "" -o "" -t -500k | nice gzip -9 -c | /usr/bin/ncftpput etc...' PS : While writing that mail, i just found that i could replace : cat %p | cstream -i "" ... with cstream -i %p ... *grins* -- ker2x Sysadmin & DBA @ http://Www.over-blog.com/