pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Ron <rjpeace@earthlink.net>
Cc: Mikael Carneholm <Mikael.Carneholm@WirelessCar.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Migration study, step 1: bulk write performance
Date: Tue, 21 Mar 2006 16:56:25 -0500
Message-ID: <2262.1142978185@sss.pgh.pa.us> (raw)
In-Reply-To: <1142975962.17883.203.camel@state.g2switchworks.com>
References: <7F10D26ECFA1FB458B89C5B4B0D72C2B088286@sesrv12.wirelesscar.com>
	<1142973890.24487.510.camel@localhost.localdomain>
	<7.0.1.0.2.20060320161133.03a0b5a8@earthlink.net>
	<1142975962.17883.203.camel@state.g2switchworks.com>

Scott Marlowe <smarlowe@g2switchworks.com> writes:
> I've also found that modest increases in commit_siblings and
> commit_delay help a lot on certain types of imports.

On a data import?  Those really should have zero effect on a
single-process workload.  Or are you doing multiple concurrent imports?

			regards, tom lane

view thread (26+ messages)  latest in thread

Message-ID: <2262.1142978185@sss.pgh.pa.us>
Permalink:  ../2262.1142978185@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2262.1142978185@sss.pgh.pa.us

copy link · copy postgr.es

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: tgl@sss.pgh.pa.us, smarlowe@g2switchworks.com, rjpeace@earthlink.net, Mikael.Carneholm@WirelessCar.com
  Subject: Re: Migration study, step 1: bulk write performance
  In-Reply-To: <2262.1142978185@sss.pgh.pa.us>

* 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