Re: Master-slave visibility order - Mailing list pgsql-hackers

From Ants Aasma
Subject Re: Master-slave visibility order
Date
Msg-id CA+CSw_uM=VFMio2s8VBki3QqvKxxEmFbzUpmc0h6FUth8Lgc9g@mail.gmail.com
Whole thread Raw
In response to Re: Master-slave visibility order  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On Fri, Aug 30, 2013 at 12:33 AM, Andres Freund <andres@2ndquadrant.com> wrote:
> FWIW, WAL is still the major bottleneck for INSERT heavy workloads. The
> per CPU overhead actually minimally increased (at least in my tests), it
> just scales noticeably better than before.

Interesting. Do you have any insight what is behind the CPU overhead?
Maybe the solution is to make WAL insertion cheap enough to not
matter. That won't be easy, but neither are the alternatives.

Regards,
Ants Aasma



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: PL/pgSQL PERFORM with CTE
Next
From: Andres Freund
Date:
Subject: Re: Variadic aggregates vs. project policy