From: jao@geophile.com
To: Vivek Khera <khera@kcilink.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints
Date: Wed, 12 May 2004 15:22:47 -0400
Message-ID: <1084389767.40a27987437da@geophile.com> (raw)
In-Reply-To: <x7k6zhlbgp.fsf@yertle.int.kciLink.com>
References: <200405101909.i4AJ9Wv09415@candle.pha.pa.us>
<40A03435.7020300@geophile.com>
<24638.1084245829@sss.pgh.pa.us>
<x7k6zhlbgp.fsf@yertle.int.kciLink.com>
Quoting Vivek Khera <khera@kcilink.com>:
> >>>>> "TL" == Tom Lane <tgl@sss.pgh.pa.us> writes:
>
> TL> Jack Orenstein <jao@geophile.com> writes:
> >> I'm looking at one case in which two successive transactions, each
> >> updating a handful of records, take 26 and 18 *seconds* (not msec) to
> >> complete. These transactions normally complete in under 30 msec.
>
> TL> I've seen installations in which it seemed that the "normal" query load
> TL> was close to saturating the available disk bandwidth, and the extra load
> TL> imposed by a background VACUUM just pushed the entire system's response
> TL> time over a cliff. In an installation that has I/O capacity to spare,
> ...
> TL> I suspect that the same observations hold true for checkpoints, though
> TL> I haven't specifically seen an installation suffering from that effect.
>
> I don't see that. But I also set checkpoint segments to about 50 on
> my big server.
But wouldn't that affect checkpoint frequency, not checkpoint cost?
Jack Orenstein
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
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: jao@geophile.com, khera@kcilink.com
Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints
In-Reply-To: <1084389767.40a27987437da@geophile.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