From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
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:23:14 -0600
Message-ID: <1142979794.17883.205.camel@state.g2switchworks.com> (raw)
In-Reply-To: <2262.1142978185@sss.pgh.pa.us>
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>
<2262.1142978185@sss.pgh.pa.us>
On Tue, 2006-03-21 at 15:56, Tom Lane wrote:
> 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?
That, and it's a machine that's doing other things. Also, a lot of the
imports are NOT bundled up into groups of transactions. i.e. lots and
lots of individual insert queries.
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: smarlowe@g2switchworks.com, tgl@sss.pgh.pa.us, rjpeace@earthlink.net, Mikael.Carneholm@WirelessCar.com
Subject: Re: Migration study, step 1: bulk write performance
In-Reply-To: <1142979794.17883.205.camel@state.g2switchworks.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