From: Greg Smith <gsmith@gregsmith.com>
To: PostgreSQL-patches <pgsql-patches@postgresql.org>
Subject: Re: Maintaining cluster order on insert
Date: Tue, 10 Jul 2007 08:52:54 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0707100815400.22343@westnet.com> (raw)
In-Reply-To: <457.1184023772@sss.pgh.pa.us>
References: <200705152223.l4FMNJa17969@momjian.us>
<464A33AB.1050401@enterprisedb.com>
<20070516003810.GI20707@nasby.net>
<464B15EF.4000808@enterprisedb.com>
<c2d9e70e0705172153g3207adb6kd4abdfdf3a9215ff@mail.gmail.com>
<464D96D6.1030608@enterprisedb.com>
<457.1184023772@sss.pgh.pa.us>
On Mon, 9 Jul 2007, Tom Lane wrote:
> The hardware is just a Dell x86_64 workstation with crappy IDE disk, so
> maybe things would look better elsewhere, but it's all I have to work
> with.
Do you have write-caching turned off on the drive so INSERTs are being
rate-limited by WAL syncs? Trying to characterize the class of setup
you're using.
The part that seemed curious to me about your results in the unpatched
version is why the first INSERT takes 2.4 seconds, while the second takes
12.2 then later ones settle from 17-23 s. I could understand the 12-23
variation, but that the first one fires off in 2.4 seems kind of fishy;
why so fast? Is there something that's just fitting in memory in that
case that's just missing in the patched version?
results-head:
...
executed DELETE in 14.770937 sec
executed VACUUM in 10.663301 sec
executed INSERT in 2.449248 sec (1st)
...
executed INSERT in 12.212027 sec (2nd)
results-patch:
...
executed DELETE in 18.062664 sec
executed VACUUM in 28.487570 sec
executed INSERT in 25.638022 sec (1st)
...
executed INSERT in 40.759404 sec (2nd)
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
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-hackers@postgresql.org
Cc: gsmith@gregsmith.com, pgsql-patches@postgresql.org
Subject: Re: Maintaining cluster order on insert
In-Reply-To: <Pine.GSO.4.64.0707100815400.22343@westnet.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