X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8336B52AC3 for ; Mon, 18 Jul 2005 16:36:28 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 36543-06 for ; Mon, 18 Jul 2005 19:36:19 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by svr1.postgresql.org (Postfix) with ESMTP id 6D9B7529C0 for ; Mon, 18 Jul 2005 16:36:18 -0300 (ADT) Received: by wproxy.gmail.com with SMTP id i34so1058753wra for ; Mon, 18 Jul 2005 12:36:20 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=iyjsSuCvUJvaUNJwO+eKhaBdUg3zPl7pUCHYZuln7EatkQvJUaxOMDMxlaQ/NTC/oRermpE4rsfbSYVVMUpykmHGGC0TLeygoEnZbr/LsynpzFrJ9FxZvH16bCrt+//MI9GWBuiTJsHwUDPRjZkm40YTGH19GXcssAkw/YM2JZY= Received: by 10.54.36.58 with SMTP id j58mr477320wrj; Mon, 18 Jul 2005 12:34:57 -0700 (PDT) Received: by 10.54.120.11 with HTTP; Mon, 18 Jul 2005 12:34:57 -0700 (PDT) Message-ID: <59d991c405071812342e290f57@mail.gmail.com> Date: Mon, 18 Jul 2005 15:34:57 -0400 From: Christopher Petrilli Reply-To: Christopher Petrilli To: Tom Lane Subject: Re: Impact of checkpoint_segments under continual load conditions Cc: Vivek Khera , pgsql-performance@postgresql.org In-Reply-To: <16394.1121715156@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <59d991c4050717100874c08a86@mail.gmail.com> <59d991c405071811457ccdd3f1@mail.gmail.com> <16394.1121715156@sss.pgh.pa.us> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.123 tagged_above=0 required=5 tests=AWL, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200507/271 X-Sequence-Number: 13512 On 7/18/05, Tom Lane wrote: > Christopher Petrilli writes: > > http://blog.amber.org/diagrams/comparison_mysql_pgsql.png >=20 > > Notice the VERY steep drop off. >=20 > 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 :-) =20 > 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 --=20 | Christopher Petrilli | petrilli@gmail.com