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 3B2E1534FC for ; Sun, 15 May 2005 17:39:55 -0300 (ADT) 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 80322-05 for ; Sun, 15 May 2005 20:39:50 +0000 (GMT) Received: from primary.talisys.com (mail.talisys.com [129.250.133.62]) by svr1.postgresql.org (Postfix) with ESMTP id 2336952A3D for ; Sun, 15 May 2005 17:39:45 -0300 (ADT) Received: from mephisto.talisys.com ([172.17.36.209]) by primary.talisys.com with esmtp (Exim 4.30) id 1DXPtl-0003vs-R0; Sun, 15 May 2005 16:39:41 -0400 Message-ID: <4287B38B.506@talisys.com> Date: Sun, 15 May 2005 13:39:39 -0700 From: William Yu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Greg Stark Cc: pgsql-performance@postgresql.org Subject: Re: ok you all win what is best opteron (I dont want a References: <4285403A.50206@bigpond.net.au> <00e201c558b1$730ffb10$797ba8c0@jfradkin> <871x8846z9.fsf@stark.xeocode.com> In-Reply-To: <871x8846z9.fsf@stark.xeocode.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200505/290 X-Sequence-Number: 12454 I say most apps because it's true. :) I would suggest that pretty much every app (other than video/audio streaming) people think are bandwidth-limited are actually latency-limited. Take the SpecFoo tests. Sure I would have rather seen SAP/TPC/etc that would be more relevant to Postgres but there aren't any apples-to-apples comparisons available yet. But there's something to consider here. What people in the past have believed is that memory bandwidth is the key to Spec numbers -- SpecFP isn't a test of floating point performance, it's a test of memory bandwidth. Or is it? Numbers for DC Opterons show lower latency/lower bandwith beating higher latency/higher bandwidth in what was supposedly bandwidth limited. What may actually be happening is extra bandwidth isn't actually used directly by the app itself -- instead the CPU uses it for prefetching to hide latency. Scrounging around for more numbers, I've found benchmarks at Anandtech that relate better to Postgres. He has a "Order Entry" OLTP app running on MS-SQL. 1xDC beats 2x1 -- 2xDC beats 4x1. order entry reads 2x248 - 235113 1x175 - 257192 4x848 - 360014 2x275 - 392643 order entry writes 2x248 - 235107 1x175 - 257184 4x848 - 360008 2x275 - 392634 order entry stored procedures 2x248 - 2939 1x175 - 3215 4x848 - 4500 2x275 - 4908 Greg Stark wrote: >William Yu writes: > > > >>It turns out the latency in a 2xDC setup is just so much lower and most apps >>like lower latency than higher bandwidth. >> >> > >You haven't tested anything about "most apps". You tested what the SpecFoo >apps prefer. If you're curious about which Postgres prefers you'll have to >test with Postgres. > >I'm not sure whether it will change the conclusion but I expect Postgres will >like bandwidth better than random benchmarks do. > > > >