limiting performance impact of wal archiving.

From: Laurent Laborde <kerdezixe(at)gmail(dot)com>
To: PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>
Subject: limiting performance impact of wal archiving.
Date: 2009-11-10 11:55:42
Message-ID: 8a1bfe660911100355l34a557ffj8244079c1fb689b5@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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/

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Kenneth Marshall 2009-11-10 13:41:24 Re: limiting performance impact of wal archiving.
Previous Message Greg Smith 2009-11-09 17:04:21 Re: CREATE TABLE slowing down significantly over time