Re: XLogFlush invoked about twice as much after 9.2 group commit enhancement

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Amit Langote <amitlangote09(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: XLogFlush invoked about twice as much after 9.2 group commit enhancement
Date: 2013-05-08 16:27:33
Message-ID: CAMkU=1y0+GYtkXqr5VbqwCxqBaNt99tfRYXOazTsBis418iVNQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 7, 2013 at 9:23 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:

> On Tue, May 7, 2013 at 12:48 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> > Anyway, I don't see this behavior change when turning on wal_debug and
> > looking in the logfiles for 'xlog flush request' messages.
>
> That could have everything to do with the hardware you're using. In
> general, the higher the cost of an fsync, the more useful it is to
> amortize that cost among concurrently committing transactions.
>

True, but that is going to happen with a proportional increase in
throughput, which he reported not seeing. At least originally. I'm not
sure what to think now.

Cheers,

Jeff

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-05-08 16:30:31 Re: Re: [COMMITTERS] pgsql: Fix permission tests for views/tables proven empty by constraint
Previous Message Dave Page 2013-05-08 15:51:12 Re: improving PL/Python builds on OS X