X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id BAA0030DF7A for ; Tue, 10 Jun 2003 19:43:59 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 35034-03 for ; Tue, 10 Jun 2003 16:43:49 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id E2B6130E359 for ; Tue, 10 Jun 2003 16:43:47 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h5AJhlU6004333; Tue, 10 Jun 2003 15:43:47 -0400 (EDT) To: Vincent van Leeuwen Cc: pgsql-performance@postgresql.org Subject: Re: FW: [ADMIN] Shared_buffers and kernel parameters, tuning In-reply-to: <20030610181247.GX1535@md2.mediadesign.nl> References: <200306100846.21875.josh@agliodbs.com> <20030610181247.GX1535@md2.mediadesign.nl> Comments: In-reply-to Vincent van Leeuwen message dated "Tue, 10 Jun 2003 20:12:48 +0200" Date: Tue, 10 Jun 2003 15:43:47 -0400 Message-ID: <4332.1055274227@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200306/40 X-Sequence-Number: 2124 Vincent van Leeuwen writes: > Halving the cpu_tuple_cost has given a very impressive performance boost > (performance roughly doubled). I'm not sure why, because the plans of the > large queries I was checking haven't changed as far as I can see, but maybe > some smaller queries I didn't bother to check are using a different plan now. That's very curious; I'd expect that parameter to have only marginal effect in the first place (unless you make huge changes in it, of course). It must have changed some plan that you didn't take note of. If you can find it I'd be interested to know. > Just to be absolutely sure: all *_cost parameters only influence the > chosen plan, right? There is absolutely nothing else influenced which > doesn't show up in an EXPLAIN ANALYZE, right? AFAIR, the only one of these parameters that the executor pays any attention to is SORT_MEM; that will determine how soon the runtime code starts to spill tuples to disk in sorts, hash tables, etc. regards, tom lane