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 E513056694 for ; Tue, 15 Mar 2005 22:44:11 +0000 (GMT) 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 49412-05 for ; Tue, 15 Mar 2005 22:44:10 +0000 (GMT) Received: from linda-1.paradise.net.nz (bm-1a.paradise.net.nz [202.0.58.20]) by svr1.postgresql.org (Postfix) with ESMTP id A5B6D5661E for ; Tue, 15 Mar 2005 22:44:06 +0000 (GMT) Received: from smtp-3.paradise.net.nz (smtp-3a.paradise.net.nz [202.0.32.196]) by linda-1.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IDF00B590HJK3@linda-1.paradise.net.nz> for pgsql-performance@postgresql.org; Wed, 16 Mar 2005 11:44:08 +1300 (NZDT) Received: from [192.168.1.11] (218-101-14-18.paradise.net.nz [218.101.14.18]) by smtp-3.paradise.net.nz (Postfix) with ESMTP id 201A8ADFDF; Wed, 16 Mar 2005 11:44:07 +1300 (NZDT) Date: Wed, 16 Mar 2005 11:44:06 +1300 From: Mark Kirkwood Subject: Re: Changing the random_page_cost default (was: In-reply-to: <6320.1110900176@sss.pgh.pa.us> To: Tom Lane Cc: Greg Sabino Mullane , pgsql-performance@postgresql.org Message-id: <42376536.10500@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8b) Gecko/20050301 References: <6320.1110900176@sss.pgh.pa.us> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.145 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/308 X-Sequence-Number: 11013 Tom Lane wrote: > "Greg Sabino Mullane" writes: > >>N.B. My own personal starting default is 2, but I thought 3 was a nice >>middle ground more likely to reach consensus here. :) > > > Your argument seems to be "this produces nice results for me", not > "I have done experiments to measure the actual value of the parameter > and it is X". I *have* done experiments of that sort, which is where > the default of 4 came from. I remain of the opinion that reducing > random_page_cost is a band-aid that compensates (but only partially) > for problems elsewhere. We can see that it's not a real fix from > the not-infrequent report that people have to reduce random_page_cost > below 1.0 to get results anywhere near local reality. That doesn't say > that the parameter value is wrong, it says that the model it's feeding > into is wrong. > I would like to second that. A while back I performed a number of experiments on differing hardware and came to the conclusion that *real* random_page_cost was often higher than 4 (like 10-15 for multi-disk raid systems). However I have frequently adjusted Pg's random_page_cost to be less than 4 - if it helped queries perform better. So yes, it looks like the model is the issue - not the value of the parameter! regards Mark