pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Daniel J. Luke <dluke@geeklair.net>
Cc: Steinar H. Gunderson <sgunderson@bigfoot.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Getting even more insert performance (250m+rows/day)
Date: Wed, 24 May 2006 16:32:25 -0500
Message-ID: <20060524213225.GM59464@pervasive.com> (raw)
In-Reply-To: <9E8E3745-64F2-4908-BF16-284CF7834760@geeklair.net>
References: <CE96DEF6-C455-4BB3-8B57-A78849A519E8@geeklair.net>
	<20060524200349.GA10753@uio.no>
	<9E8E3745-64F2-4908-BF16-284CF7834760@geeklair.net>

On Wed, May 24, 2006 at 04:09:54PM -0400, Daniel J. Luke wrote:
> On May 24, 2006, at 4:03 PM, Steinar H. Gunderson wrote:
> >Have you tried fiddling with the checkpointing settings? Check your  
> >logs --
> >if you get a warning about checkpoints being too close together,  
> >that should
> >give you quite some boost.
> 
> no warnings in the log (I did change the checkpoint settings when I  
> set up the database, but didn't notice an appreciable difference in  
> insert performance).

Keep in mind that the default warning time of 30 seconds is pretty
conservative; you'd want to bump that up to 300 seconds or so, probably.

As for the suggestion of multiple insert runs at a time, I suspect that
would just result in a lot of contention for some mutex/semaphore in the
index.

Your best bet really is to run gprof and post those results. It's also
possible that this is fixed be a recent patch to HEAD that reduces the
amount of traffic on the index metapage, something gprof would probably
confirm.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (17+ messages)  latest in thread

Message-ID: <20060524213225.GM59464@pervasive.com>
Permalink:  ../20060524213225.GM59464@pervasive.com/
Also on:    postgresql.org/message-id/20060524213225.GM59464@pervasive.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: jnasby@pervasive.com, dluke@geeklair.net, sgunderson@bigfoot.com
  Subject: Re: Getting even more insert performance (250m+rows/day)
  In-Reply-To: <20060524213225.GM59464@pervasive.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox