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 56C85D1E274 for ; Wed, 12 May 2004 15:58:21 -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 38636-08 for ; Wed, 12 May 2004 15:58:00 -0300 (ADT) Received: from lorax.kcilink.com (lorax.kcilink.com [206.112.95.1]) by svr1.postgresql.org (Postfix) with ESMTP id 659B3D1E26B for ; Wed, 12 May 2004 15:57:58 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by lorax.kcilink.com (Postfix) with ESMTP id A10403FB1 for ; Wed, 12 May 2004 14:57:59 -0400 (EDT) Received: from lorax.kcilink.com ([127.0.0.1]) by localhost (lorax.kcilink.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 42731-08-2 for ; Wed, 12 May 2004 14:57:58 -0400 (EDT) Received: by lorax.kcilink.com (Postfix, from userid 8) id ACB473FAF; Wed, 12 May 2004 14:57:58 -0400 (EDT) To: pgsql-performance@postgresql.org Path: not-for-mail From: Vivek Khera Newsgroups: ml.postgres.performance Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints Date: Wed, 12 May 2004 14:57:58 -0400 Organization: Khera Communications, Inc., Rockville, MD Lines: 31 Message-ID: References: <200405101909.i4AJ9Wv09415@candle.pha.pa.us> <40A03435.7020300@geophile.com> <24638.1084245829@sss.pgh.pa.us> NNTP-Posting-Host: yertle.kcilink.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: lorax.kcilink.com 1084388278 14464 65.205.34.180 (12 May 2004 18:57:58 GMT) X-Complaints-To: daemon@kciLink.com NNTP-Posting-Date: Wed, 12 May 2004 18:57:58 +0000 (UTC) User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Reasonable Discussion, berkeley-unix) Cancel-Lock: sha1:xdoNdGrsXUv8IumQkajGbH/YP6s= X-Virus-Scanned: by amavisd-new at kcilink.com 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/113 X-Sequence-Number: 6944 >>>>> "TL" == Tom Lane writes: TL> Jack Orenstein 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, me stand up waving hand... ;-) This is my only killer problem left. I always peg my disk usage at 100% when vacuum runs, and other queries are slow too. When not running vacuum, my queries are incredibly zippy fast, including joins and counts and group by's on upwards of 100k rows at a time. 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. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-869-4449 x806 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/