From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | MauMau <maumau307(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Could synchronous streaming replication really degrade the performance of the primary? |
Date: | 2012-05-09 13:58:04 |
Message-ID: | CAHyXU0w4vxULonSa+bJgALDK6gYHyvXcGj-VaZNE717ttkfXoA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, May 9, 2012 at 8:06 AM, MauMau <maumau307(at)gmail(dot)com> wrote:
> Hello,
>
> I've heard from some people that synchronous streaming replication has
> severe performance impact on the primary. They said that the transaction
> throughput of TPC-C like benchmark (perhaps DBT-2) decreased by 50%. I'm
> sorry I haven't asked them about their testing environment, because they
> just gave me their experience. They think that this result is much worse
> than some commercial database.
I can't speak for other databases, but it's only natural to assume
that tps must drop. At minimum, you have to add the latency of
communication and remote sync operation to your transaction time. For
very short transactions this adds up to a lot of extra work relative
to the transaction itself.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Klemme | 2012-05-09 15:41:00 | Re: Could synchronous streaming replication really degrade the performance of the primary? |
Previous Message | Clemens Eisserer | 2012-05-09 13:27:39 | Re: Any disadvantages of using =ANY(ARRAY()) instead of IN? |