From: Christopher Petrilli <petrilli@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Vivek Khera <vivek@khera.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Impact of checkpoint_segments under continual load conditions
Date: Mon, 18 Jul 2005 15:34:57 -0400
Message-ID: <59d991c405071812342e290f57@mail.gmail.com> (raw)
In-Reply-To: <16394.1121715156@sss.pgh.pa.us>
References: <59d991c4050717100874c08a86@mail.gmail.com>
<A50B8A1F-71A1-4F63-A5F4-1AA58F89557D@khera.org>
<59d991c405071811457ccdd3f1@mail.gmail.com>
<16394.1121715156@sss.pgh.pa.us>
On 7/18/05, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Christopher Petrilli <petrilli@gmail.com> writes:
> > http://blog.amber.org/diagrams/comparison_mysql_pgsql.png
>
> > Notice the VERY steep drop off.
>
> Hmm. Whatever that is, it's not checkpoint's fault. I would interpret
> the regular upticks in the Postgres times (every several hundred
> iterations) as being the effects of checkpoints. You could probably
> smooth out those peaks some with appropriate hacking on bgwriter
> parameters, but that's not the issue at hand (is it?).
I tried hacking that, turning it up to be more agressive, it got
worse. Turned it down, it got worse :-)
> I have no idea at all what's causing the sudden falloff in performance
> after about 10000 iterations. COPY per se ought to be about a
> constant-time operation, since APPEND is (or should be) constant-time.
> What indexes, foreign keys, etc do you have on this table? What else
> was going on at the time?
The table has 15 columns, 5 indexes (character, inet and timestamp).
No foreign keys. The only other thing running on the machine was the
application actually DOING the benchmarking, written in Python
(psycopg), but it was, according to top, using less than 1% of the
CPU. It was just talking through a pipe to a psql prompt to do the
COPY.
Chris
--
| Christopher Petrilli
| petrilli@gmail.com
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: petrilli@gmail.com, tgl@sss.pgh.pa.us, vivek@khera.org
Subject: Re: Impact of checkpoint_segments under continual load conditions
In-Reply-To: <59d991c405071812342e290f57@mail.gmail.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