Skip site navigation (1) Skip section navigation (2)

Re: Moving more work outside WALInsertLock

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Moving more work outside WALInsertLock
Date: 2012-01-07 09:31:04
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On 25.12.2011 21:48, Robert Haas wrote:
> On Fri, Dec 23, 2011 at 2:54 PM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com>  wrote:
>> Sorry. Last minute changes, didn't retest properly.. Here's another attempt.
> I tried this one out on Nate Boley's system.  Looks pretty good.
> [pgbench results]

Great, thanks for the testing!

> Unfortunately, it does look like there is some raw loss of performance
> when WALInsertLock is NOT badly contended; hence the drop-off at a
> single client on permanent tables, and up through 24 clients on
> unlogged tables.

Hmm, I haven't been able to put my finger on what's causing that.

Anyway, here's a new version of the patch. It no longer busy-waits for 
in-progress insertions to finish, and handles xlog-switches. This is now 
feature-complete. It's a pretty complicated patch, so I would appreciate 
more eyeballs on it. And benchmarking again.

   Heikki Linnakangas

Attachment: xloginsert-scale-4.patch
Description: text/x-diff (95.8 KB)

In response to


pgsql-hackers by date

Next:From: Simon RiggsDate: 2012-01-07 10:14:30
Subject: Re: 16-bit page checksums for 9.2
Previous:From: Heikki LinnakangasDate: 2012-01-07 08:12:39

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group