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 42A5DD1CCCA for ; Thu, 22 Apr 2004 18:22: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 25992-09 for ; Thu, 22 Apr 2004 18:22:23 -0300 (ADT) Received: from tht.net (vista.tht.net [216.126.88.2]) by svr1.postgresql.org (Postfix) with ESMTP id A515ED1CCA8 for ; Thu, 22 Apr 2004 18:22:20 -0300 (ADT) Received: from [134.22.70.203] (dyn-70-203.tor.dsl.tht.net [134.22.70.203]) by tht.net (Postfix) with ESMTP id 1756376A2B; Thu, 22 Apr 2004 17:22:26 -0400 (EDT) Subject: Re: Wierd context-switching issue on Xeon patch for 7.4.1 From: Rod Taylor To: Tom Lane Cc: Josh Berkus , Bruce Momjian , pg@fastcrypt.com, Paul Tuckfield , Anjan Dave , Neil Conway , Dirk =?ISO-8859-1?Q?Lutzeb=E4ck?= , Postgresql Performance In-Reply-To: <8583.1082656553@sss.pgh.pa.us> References: <200404220456.i3M4uFv04710@candle.pha.pa.us> <20171.1082610827@sss.pgh.pa.us> <200404221037.10097.josh@agliodbs.com> <8583.1082656553@sss.pgh.pa.us> Content-Type: text/plain Message-Id: <1082668930.94537.0.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Thu, 22 Apr 2004 17:22:11 -0400 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200404/394 X-Sequence-Number: 6694 On Thu, 2004-04-22 at 13:55, Tom Lane wrote: > Josh Berkus writes: > > This may be a moot point, since you've stated that changing the loop timing > > won't solve the problem, but what about making the test part of make? I > > don't think too many systems are going to change processor architectures once > > in production, and those that do can be told to re-compile. > > Having to recompile to run on single- vs dual-processor machines doesn't > seem like it would fly. Is it something the postmaster could quickly determine and set a global during the startup cycle?