Re: performance for high-volume log insertion

From: Glenn Maynard <glennfmaynard(at)gmail(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: performance for high-volume log insertion
Date: 2009-05-02 04:13:19
Message-ID: bd36f99e0905012113g1204133t5137b58c4d502284@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, May 1, 2009 at 8:29 PM, PFC <lists(at)peufeu(dot)com> wrote:
>        Roundtrips can be quite fast but they have a hidden problem, which is
> that everything gets serialized.

The client and server will serialize, but what usually matters most is
avoiding serializing against disk I/O--and that's why write-back
caching exists. There's still a benefit to pipelining (not everything
the db might need to read to complete the write will always be in
cache), but if everything was being serialized it'd be an order of
magnitude worse. That's why running each insert in a separate
transaction is so much slower; in that case, it *will* serialize
against the disk (by default).

--
Glenn Maynard

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Laurent Laborde 2009-05-04 08:10:08 high shared buffer and swap
Previous Message david 2009-05-02 00:49:38 Re: performance for high-volume log insertion