X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 7F964D1E98D for ; Mon, 19 Apr 2004 14:50:27 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 31056-02 for ; Mon, 19 Apr 2004 14:50:25 -0300 (ADT) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id DD481D1E95F for ; Mon, 19 Apr 2004 14:50:23 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 4900262; Mon, 19 Apr 2004 10:51:46 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: Tom Lane , lutzeb@aeccom.com Subject: Re: Wierd context-switching issue on Xeon Date: Mon, 19 Apr 2004 10:50:12 -0700 User-Agent: KMail/1.4.3 Cc: pgsql-performance@postgreSQL.org, Neil Conway References: <200311251419.36771.josh@agliodbs.com> <407EFC95.5070805@aeccom.com> <11437.1082324861@sss.pgh.pa.us> In-Reply-To: <11437.1082324861@sss.pgh.pa.us> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200404191050.12833.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/272 X-Sequence-Number: 6572 Tom, > So in the short term I think we have to tell people that Xeon MP is not > the most desirable SMP platform to run Postgres on. (Josh thinks that > the specific motherboard chipset being used in these machines might > share some of the blame too. I don't have any evidence for or against > that idea, but it's certainly possible.) I have 3 reasons for thinking this: 1) the ServerWorks chipset is present in the fully documented cases that we have of this problem so far. This is notable becuase the SW is notorious for poor manufacturing quality, so much so that the company that made them is currently in receivership. These chips were so bad that Dell was forced to recall several hundred of it's 2650's, where the motherboards caught fire! 2) the main defect of the SW is the NorthBridge, which could conceivably adversely affect traffic between RAM and the processor cache. 3) XeonMP is a very popular platform thanks to Dell, and we are not seeing more problem reports than we are. The other thing I'd like your comment on, Tom, is that Dirk appears to have reported that when he installed a non-bigmem kernel, the issue went away. Dirk, is this correct? -- Josh Berkus Aglio Database Solutions San Francisco