From: Michal Taborsky <michal@taborsky.cz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Slow INSERT
Date: Tue, 29 Jun 2004 17:47:32 +0200
Message-ID: <40E18F14.4000600@taborsky.cz> (raw)
In-Reply-To: <29835.1088522568@sss.pgh.pa.us>
References: <40E160E6.4080105@taborsky.cz>
<29095.1088519446@sss.pgh.pa.us>
<40E1863B.9070208@taborsky.cz>
<29835.1088522568@sss.pgh.pa.us>
Tom Lane wrote:
> Actually, the simpler theory is that the slowdown is caused by
> background checkpoint operations. Now a checkpoint would slow
> *everything* down not only this one insert, so maybe that's not
> the right answer either, but it's my next idea. You could check
> this to some extent by manually issuing a CHECKPOINT command and
> seeing if you get an insert hiccup. Note though that closely
> spaced checkpoints will have less effect, because less I/O will
> be triggered when not much has changed since the last one. So
> you'd want to wait a bit between experiments.
Aha! This is really the case. I've let the test run and issued manual
CHECKPOINT command. The command itself took about 3 secs and during that
time I had some slow INSERTS. So we know the reason.
I've read the discussion in "Trying to minimize the impact of
checkpoints" thread and I get it, that there is nothing I can do about
it. Well, we'll have to live with that, at least until 7.5.
Thanks of the help all the same.
--
Michal Taborsky
http://www.taborsky.cz
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: michal@taborsky.cz, tgl@sss.pgh.pa.us
Subject: Re: Slow INSERT
In-Reply-To: <40E18F14.4000600@taborsky.cz>
* 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