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 926D952AB8 for ; Fri, 29 Jul 2005 16:21:57 -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 21752-07 for ; Fri, 29 Jul 2005 19:21:54 +0000 (GMT) Received: from mx1.neopolitan.us (mx1.neopolitan.us [65.87.16.224]) by svr1.postgresql.org (Postfix) with ESMTP id 0CADD52AC2 for ; Fri, 29 Jul 2005 16:21:53 -0300 (ADT) Received: from [65.87.16.98] (HELO [10.0.0.221]) by mx1.neopolitan.us (CommuniGate Pro SMTP 4.2.10) with ESMTP id 10168090; Fri, 29 Jul 2005 12:21:54 -0700 User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Fri, 29 Jul 2005 12:21:53 -0700 Subject: Re: Performance problems on 4/8way Opteron (dualcore) From: "J. Andrew Rogers" To: , Cc: Dirk Lutzeb=?ISO-8859-1?B?5A==?=ck , Sven Geisler Message-ID: In-Reply-To: <200507291046.10318.josh@agliodbs.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.312 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST X-Spam-Level: * X-Archive-Number: 200507/484 X-Sequence-Number: 13725 On 7/29/05 10:46 AM, "Josh Berkus" wrote: >> does anybody have expierence with this machine (4x 875 dual core Opteron >> CPUs)? > > Nope. I suspect that you may be the first person to report in on > dual-cores. There may be special compile issues with dual-cores that > we've not yet encountered. There was recently a discussion of similar types of problems on a couple of the supercomputing lists, regarding surprisingly substandard performance from large dual-core opteron installations. The problem as I remember it boiled down to the Linux kernel handling memory/process management very badly on large dual core systems -- pathological NUMA behavior. However, this problem has apparently been fixed in Linux v2.6.12+, and using the more recent kernel on large dual core systems generated *massive* performance improvements on these systems for the individuals with this issue. Using the patched kernel, one gets the performance most people were expecting. The v2.6.12+ kernels are a bit new, but they contain a very important performance patch for systems like the one above. It would definitely be worth testing if possible. J. Andrew Rogers