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 E90E756846 for ; Tue, 15 Mar 2005 05:30:51 +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 78633-09 for ; Tue, 15 Mar 2005 05:30:48 +0000 (GMT) Received: from stark.xeocode.com (stark.xeocode.com [216.58.44.227]) by svr1.postgresql.org (Postfix) with ESMTP id 1070156843 for ; Tue, 15 Mar 2005 05:30:45 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=stark.xeocode.com) by stark.xeocode.com with smtp (Exim 3.36 #1 (Debian)) id 1DB4dd-0002Sj-00 for ; Tue, 15 Mar 2005 00:30:41 -0500 To: pgsql-performance@postgresql.org Subject: Re: cpu_tuple_cost From: Gregory Stark Date: 15 Mar 2005 00:30:41 -0500 Message-ID: <87psy1mq66.fsf@stark.xeocode.com> Lines: 19 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.02 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/292 X-Sequence-Number: 10997 Bruce Momjian wrote: > Agreed. I think we should reduce it at least to 3. Note that changing it from 4 to 3 or even 2 is unlikely to really change much. Many of the plans people complain about turn out to have critical points closer to 1.2 or 1.1. The only reason things work out better with such low values is because people have data sets that fit more or less entirely in RAM. So values close to 1 or even equal to 1 actually represent the reality. The "this day and age" argument isn't very convincing. Hard drive capacity growth has far outstripped hard drive seek time and bandwidth improvements. Random access has more penalty than ever. -- greg