pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Aleksej Trofimov <aleksej.trofimov@ruptela.lt>
To: Claudio Freire <klaussfreire@gmail.com>
Cc: sgupta <saurabh.b85@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgresql Replication Performance
Date: Thu, 29 Dec 2011 18:05:36 +0200
Message-ID: <4EFC8FD0.9020100@ruptela.lt> (raw)
In-Reply-To: <CAGTBQpa98=qcPDfyGTcXJibjUrNjio=xuYSrq67Bhc7-naqn8A@mail.gmail.com>
References: <1325151184846-5107278.post@n5.nabble.com>
	<4EFC7A49.6070107@ruptela.lt>
	<CAGTBQpa98=qcPDfyGTcXJibjUrNjio=xuYSrq67Bhc7-naqn8A@mail.gmail.com>

On 12/29/2011 05:00 PM, Claudio Freire wrote:
> Second, is that WAL activity on streaming replication or WAL shipping
> is documented to contain more data than on non-replicated setups. What
> is not clear is how much more data. This not only affects our network
> bandwidth estimations, but also I/O load on the master server, slowing
> writes (and some reads that cannot happen on the slave).
Our database has about 2MB/s writes on the WAL array, we had about 160 
IOPS in average when replications was switched off, and 165-170 IOPS in 
replication. This I think could be explained with statistical error, so 
we have not experienced any I/O load on our master server since 
replication was configured.


-- 
Best regards

Aleksej Trofimov




view thread (7+ messages)  latest in thread

Message-ID: <4EFC8FD0.9020100@ruptela.lt>
Permalink:  ../4EFC8FD0.9020100@ruptela.lt/
Also on:    postgresql.org/message-id/4EFC8FD0.9020100@ruptela.lt

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: aleksej.trofimov@ruptela.lt, klaussfreire@gmail.com, saurabh.b85@gmail.com
  Subject: Re: Postgresql Replication Performance
  In-Reply-To: <4EFC8FD0.9020100@ruptela.lt>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox