X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 984ABDBAB1 for ; Fri, 18 Nov 2005 12:14:33 -0400 (AST) 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 54005-06 for ; Fri, 18 Nov 2005 16:14:31 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from unicorn.rentec.com (unicorn.rentec.com [216.223.240.9]) by svr1.postgresql.org (Postfix) with ESMTP id D644DDBAAE for ; Fri, 18 Nov 2005 12:14:29 -0400 (AST) Received: from ram.rentec.com (mailhost [192.5.35.66]) by unicorn.rentec.com (8.13.1/8.12.1) with ESMTP id jAIGDeP9024547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Nov 2005 11:13:41 -0500 (EST) X-Source: non-mednet Received: from [172.26.132.145] (hoopoe.rentec.com [172.26.132.145]) by ram.rentec.com (8.13.1/8.12.1) with ESMTP id jAIGD9qD006841; Fri, 18 Nov 2005 11:13:09 -0500 (EST) Message-ID: <437DFDB8.1030208@rentec.com> Date: Fri, 18 Nov 2005 11:13:44 -0500 From: Alan Stange Reply-To: stange@rentec.com Organization: Renaissance Technologies Corp. User-Agent: Thunderbird 1.5 (X11/20051025) MIME-Version: 1.0 To: Luke Lonergan CC: Dave Cramer , Greg Stark , Joshua Marsh , pgsql-performance@postgresql.org Subject: Re: Hardware/OS recommendations for large databases ( References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Logged: Logged by unicorn.rentec.com as jAIGDeP9024547 at Fri Nov 18 11:13:41 2005 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.019 required=5 tests=[AWL=0.019] X-Spam-Score: 0.019 X-Spam-Level: X-Archive-Number: 200511/375 X-Sequence-Number: 15632 Luke Lonergan wrote: > Alan, > > On 11/18/05 6:46 AM, "Alan Stange" wrote: > > That's 3 hours under load, with 80 compute clients beating on the > database at the same time. We have the stats turned way up, so the > analyze tends to read a big chunk of the tables a second time as > well. We typically don't have three hours a day of idle time. > > > So I guess you’re saying you don’t know what your I/O rate is? No, I'm say *you* don't know what my IO rate is. I told you in my initial post that I was observing numbers in excess of what you claiming, but you seemed to think I didn't know how to measure an IO rate. I should note too that our system uses about 20% of a single cpu when performing a table scan at >100MB/s of IO. I think you claimed the system would be cpu bound at this low IO rate. Cheers, -- Alan