X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 8D903D1B289 for ; Mon, 10 May 2004 23:33:58 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 70380-01 for ; Mon, 10 May 2004 23:33:41 -0300 (ADT) Received: from candle.pha.pa.us (candle.pha.pa.us [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 3525CD1B282 for ; Mon, 10 May 2004 23:33:35 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id i4B2XRN00185; Mon, 10 May 2004 22:33:27 -0400 (EDT) From: Bruce Momjian Message-Id: <200405110233.i4B2XRN00185@candle.pha.pa.us> Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints In-Reply-To: <40A03435.7020300@geophile.com> To: Jack Orenstein Date: Mon, 10 May 2004 22:33:27 -0400 (EDT) Cc: pgsql-performance@postgresql.org X-Mailer: ELM [version 2.4ME+ PL108 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/67 X-Sequence-Number: 6898 Jack Orenstein wrote: > Bruce Momjian wrote: > > jao@geophile.com wrote: > > > >>4. I understand that a "background writer" is being contemplated for > >>7.5. Will that replace or augment the checkpoint process? Any > >>comments on how that work will apply to my problem would be > >>appreciated. I wouldn't mind seeing the average performance, > >>(without the spikes) go up -- let's say -- 10%, in exchange for > >>more uniform performance. These spikes are a real problem. > > > > > > The background writer is designed to address your specific problem. We > > will stil checkpoint, but the spike should be greatly minimized. > > > > Thanks. Do you know when 7.5 is expected to be released? 3-6 months. > Until then, is a workaround known? Also, are the delays I'm seeing out of the ordinary? > 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. Wow. Others might know the answer to that. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073