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 92950D1E275 for ; Wed, 12 May 2004 16:25:19 -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 46054-05 for ; Wed, 12 May 2004 16:24:59 -0300 (ADT) Received: from black.geophile.com (h004005242b8e.ne.client2.attbi.com [24.91.49.146]) by svr1.postgresql.org (Postfix) with ESMTP id 61520D1E26E for ; Wed, 12 May 2004 16:24:57 -0300 (ADT) Received: from black.geophile.com (localhost.localdomain [127.0.0.1]) by black.geophile.com (8.12.8/8.12.8) with ESMTP id i4CJMlxY002022; Wed, 12 May 2004 15:22:48 -0400 Received: (from apache@localhost) by black.geophile.com (8.12.8/8.12.8/Submit) id i4CJMlCU002020; Wed, 12 May 2004 15:22:47 -0400 X-Authentication-Warning: black.geophile.com: apache set sender to jao@geophile.com using -f Received: from 64.119.142.34 ([64.119.142.34]) by geophile.com (IMP) with HTTP for ; Wed, 12 May 2004 15:22:47 -0400 Message-ID: <1084389767.40a27987437da@geophile.com> Date: Wed, 12 May 2004 15:22:47 -0400 From: jao@geophile.com To: Vivek Khera Cc: pgsql-performance@postgresql.org Subject: Re: Configuring PostgreSQL to minimize impact of checkpoints References: <200405101909.i4AJ9Wv09415@candle.pha.pa.us> <40A03435.7020300@geophile.com> <24638.1084245829@sss.pgh.pa.us> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.2 X-Originating-IP: 64.119.142.34 X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.3 tagged_above=0.0 required=5.0 tests=NO_REAL_NAME X-Spam-Level: X-Archive-Number: 200405/115 X-Sequence-Number: 6946 Quoting Vivek Khera : > >>>>> "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, > ... > 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.