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 8D51E9FB35D for ; Fri, 22 Sep 2006 05:59:38 -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 87144-03 for ; Fri, 22 Sep 2006 08:59:28 +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 D91989FB353 for ; Fri, 22 Sep 2006 05:59:27 -0300 (ADT) Received: from [127.0.0.1] (h8441139206.dsl.speedlinq.nl [84.41.139.206]) by olive.qinip.net (Postfix) with ESMTP id 302E218059; Fri, 22 Sep 2006 10:59:23 +0200 (MEST) Message-ID: <4513A5EF.7000201@tweakers.net> Date: Fri, 22 Sep 2006 10:59:27 +0200 From: Arjen van der Meijden User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Hannes Dorbath CC: pgsql-performance@postgresql.org Subject: Re: Opteron vs. Xeon "benchmark" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 0638-0, 19-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/297 X-Sequence-Number: 20983 Try the translation ;) http://tweakers.net/reviews/646/13 On 22-9-2006 10:32 Hannes Dorbath wrote: > A colleague pointed me to this site tomorrow: > > http://tweakers.net/reviews/642/13 > > I can't read the language, so can't get a grip on what exactly the > "benchmark" was about. > > Their diagrams show `Request per seconds'. What should that mean? How > many connections PG accepted per second? So they measured the OS fork > performance? Should that value be of any interrest? Anyone with heavy > OLTP workload will use persistent connections or a connection pool in > front. > > Do they mean TPS? That woulnd't make much sense in a CPU benchmark, as > OLTP workload is typically limited by the disc subsystem. > > Can someone enlighten me what this site is about? > >