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 6645055683 for ; Wed, 16 Mar 2005 19:45:58 +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 81666-05 for ; Wed, 16 Mar 2005 19:45:40 +0000 (GMT) Received: from stark.xeocode.com (stark.xeocode.com [216.58.44.227]) by svr1.postgresql.org (Postfix) with ESMTP id 214AF56702 for ; Wed, 16 Mar 2005 19:45:39 +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 1DBeSM-0001Cu-00; Wed, 16 Mar 2005 14:45:26 -0500 To: Josh Berkus Cc: Greg Stark , David Brown , Gregory Stark Subject: Re: cpu_tuple_cost References: <87psy1mq66.fsf@stark.xeocode.com> <42377293.1010801@bigpond.net.au> <87acp4kq9o.fsf@stark.xeocode.com> <200503161003.10916.josh@agliodbs.com> In-Reply-To: <200503161003.10916.josh@agliodbs.com> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 16 Mar 2005 14:45:26 -0500 Message-ID: <87psxzjrxl.fsf@stark.xeocode.com> Lines: 24 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 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.019 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/340 X-Sequence-Number: 11045 Josh Berkus writes: > Although I can point out that you left out the fact that the disk needs to do > a seek to find the beginning of the seq scan area, and even then some file > fragmentation is possible. Finally, I've never seen PostgreSQL manage more > than 70% of the maximum read rate, and in most cases more like 30%. Hm. I just did a quick test. It wasn't really long enough to get a good estimate, but it seemed to reach about 30MB/s on this drive that's only capable of 40-50MB/s depending on the location on the platters. That's true though, some of my calculated 25% random seeks could be caused by fragmentation. But it seems like that would be a small part. > > So what's going on with the empirically derived value of 4? > > It's not empirically derived; it's a value we plug into an > internal-to-postgresql formula. I thought Tom said he got the value by doing empirical tests. -- greg