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 D71CDD1CC8D for ; Sun, 18 Apr 2004 15:47:45 -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 09515-06 for ; Sun, 18 Apr 2004 15:47:45 -0300 (ADT) Received: from net2.micro-automation.com (net2.micro-automation.com [64.7.141.29]) by svr1.postgresql.org (Postfix) with SMTP id 7777CD1C515 for ; Sun, 18 Apr 2004 15:47:42 -0300 (ADT) Received: (qmail 625 invoked from network); 18 Apr 2004 18:47:38 -0000 Received: from dcdsl.ebox.com (HELO ?192.168.1.36?) (davec@64.7.143.116) by net2.micro-automation.com with SMTP; 18 Apr 2004 18:47:38 -0000 Subject: Re: Toooo many context switches (maybe SLES8?) From: Dave Cramer Reply-To: pg@fastcrypt.com To: Josh Berkus Cc: Tom Lane , Joe Conway , Dirk =?ISO-8859-1?Q?Lutzeb=E4ck?= , pgsql-performance@postgresql.org In-Reply-To: <200404151337.00273.josh@agliodbs.com> References: <407E7B99.3050306@aeccom.com> <407EBA89.6080007@joeconway.com> <20498.1082057841@sss.pgh.pa.us> <200404151337.00273.josh@agliodbs.com> Content-Type: text/plain Organization: Cramer Consulting Message-Id: <1082314193.1557.44.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 18 Apr 2004 14:49:53 -0400 Content-Transfer-Encoding: 7bit X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (http://amavis.org/) X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/248 X-Sequence-Number: 6548 Isn't this a linux kernel issue ? My understanding is that the scheduler doesn't know that 2 of the CPU's are actually the same underlying hardware and sometimes two contexts end up fighting for the same underlying chip? --dc-- On Thu, 2004-04-15 at 16:37, Josh Berkus wrote: > Folks, > > > I am currently chasing what seems to be the same issue: massive context > > swapping on a dual Xeon system. I tried back-patching the above-mentioned > > patch ... it helps a little but by no means solves the problem ... > > BTW, I'm currently pursuing the possibility that this has something to do with > the ServerWorks chipset on those motherboards. If anyone knows a high-end > hardware+linux kernel geek I can corner, I'd appreciate it. > > Maybe I should contact OSDL ... -- Dave Cramer 519 939 0336 ICQ # 14675561