X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 8A8E59FB345 for ; Fri, 8 Sep 2006 13:46:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 47094-05-3 for ; Fri, 8 Sep 2006 16:46:01 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from olive.qinip.net (olive.qinip.net [62.100.30.40]) by postgresql.org (Postfix) with ESMTP id 25E589F9945 for ; Fri, 8 Sep 2006 13:45:48 -0300 (ADT) Received: from [127.0.0.1] (h8441139206.dsl.speedlinq.nl [84.41.139.206]) by olive.qinip.net (Postfix) with ESMTP id C1E1B1826F; Fri, 8 Sep 2006 18:45:44 +0200 (MEST) Message-ID: <45019E3C.2010603@tweakers.net> Date: Fri, 08 Sep 2006 18:45:48 +0200 From: Arjen van der Meijden User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: Stefan Kaltenbrunner CC: Dave Cramer , pgsql-performance@postgresql.org Subject: Re: Xeon Woodcrest/Dempsey vs Opteron Socket F/940 with References: <450104C8.2070709@tweakers.net> <398A981F-5DE4-4845-ACF7-BB5777CECF05@fastcrypt.com> <45016590.6050905@tweakers.net> <4D290F9E-240D-4F21-A182-8E193BEEA5CB@fastcrypt.com> <450193DB.7080104@tweakers.net> <450197EA.7040900@kaltenbrunner.cc> In-Reply-To: <450197EA.7040900@kaltenbrunner.cc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 0636-3, 08-09-2006), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200609/55 X-Sequence-Number: 20741 On 8-9-2006 18:18 Stefan Kaltenbrunner wrote: > > interesting - so this is a mostly CPU-bound benchmark ? > Out of curiousity have you done any profiling on the databases under > test to see where they are spending their time ? Yeah, it is. We didn't do any profiling. We had a Sun-engineer visit us to see why MySQL performed so bad on the T2000 and he has done some profiling, but that is of course just a small and specific part of our total set of benchmarks. Postgresql was mostly left out of that picture since it performed pretty well (although it may even do better with more tuning and profiling). We are/were not interested enough in the profiling-part, since we just run the benchmark to see how fast each system is. Not really to see how fast each database is or why a database is faster on X or Y. The latter is of course pretty interesting, but also requires quite a bit of knowledge of the internals and a bit of time to analyze the results... Best regards, Arjen