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 C83D03A5D79 for ; Wed, 12 Jan 2005 17:25:34 +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 49312-01 for ; Wed, 12 Jan 2005 17:25:28 +0000 (GMT) Received: from stark.xeocode.com (gsstark.mtl.istop.com [66.11.160.162]) by svr1.postgresql.org (Postfix) with ESMTP id 8AC193A5D76 for ; Wed, 12 Jan 2005 17:25:27 +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 1ComFI-0002c2-00; Wed, 12 Jan 2005 12:25:24 -0500 To: alex@neteconomist.com Cc: Greg Stark , Merlin Moncure , pgsql-performance@postgresql.org Subject: Re: which dual-CPU hardware/OS is fastest for PostgreSQL? References: <6EE64EF3AB31D5448D0007DD34EEB3412A75A3@Herge.rcsinc.local> <87zmzg0ycq.fsf@stark.xeocode.com> <33c6269f050112085763aff4a6@mail.gmail.com> In-Reply-To: <33c6269f050112085763aff4a6@mail.gmail.com> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 12 Jan 2005 12:25:23 -0500 Message-ID: <87y8eyzhj0.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.051 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/152 X-Sequence-Number: 9842 Alex Turner writes: > Infact the cache hit ratio that Oracle suggests is the minimum good > value is 95%. Anything below that is bad news. Well that seems very workload dependent. No amount of cache is going to be able to achieve that for a DSS system chugging sequentially through terabytes of data. Whereas for OLTP systems I would wouldn't be surprised to see upwards of 99% hit rate. Note that a high cache hit rate can also be a sign of a problem. After all, it means the same data is being accessed repeatedly which implicitly means something is being done inefficiently. For an SQL database it could mean the query plans are suboptimal. On several occasions we found Oracle behaving poorly despite excellent cache hit rates because it was doing a sequential scan of a moderately sized table instead of an index lookup. The table was small enough to fit in RAM but large enough to consume a significant amount of cpu, especially with the query being run thousands of times per minute. -- greg