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 BAFCFD1CC8D for ; Mon, 19 Apr 2004 09:30:16 -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 85835-08 for ; Mon, 19 Apr 2004 09:30:13 -0300 (ADT) Received: from net2.micro-automation.com (net2.micro-automation.com [64.7.141.29]) by svr1.postgresql.org (Postfix) with SMTP id 681C3D1B515 for ; Mon, 19 Apr 2004 09:30:09 -0300 (ADT) Received: (qmail 12810 invoked from network); 19 Apr 2004 12:30:08 -0000 Received: from dcdsl.ebox.com (HELO ?192.168.1.36?) (davec@64.7.143.116) by net2.micro-automation.com with SMTP; 19 Apr 2004 12:30:08 -0000 Subject: Re: Wierd context-switching issue on Xeon From: Dave Cramer Reply-To: pg@fastcrypt.com To: Tom Lane Cc: lutzeb@aeccom.com, Josh Berkus , pgsql-performance@postgresql.org, Neil Conway In-Reply-To: <14394.1082344796@sss.pgh.pa.us> References: <200311251419.36771.josh@agliodbs.com> <200404151039.17763.josh@agliodbs.com> <407EE93F.3090705@aeccom.com> <200404151335.27762.josh@agliodbs.com> <407EFC95.5070805@aeccom.com> <11437.1082324861@sss.pgh.pa.us> <1082331281.1557.47.camel@localhost.localdomain> <13960.1082341222@sss.pgh.pa.us> <14394.1082344796@sss.pgh.pa.us> Content-Type: text/plain Organization: Cramer Consulting Message-Id: <1082377953.1554.77.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 19 Apr 2004 08:32:33 -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/268 X-Sequence-Number: 6568 Here's an interesting link that suggests that hyperthreading would be much worse. http://groups.google.com/groups?q=hyperthreading+dual+xeon+idle&start=10&hl=en&lr=&ie=UTF-8&c2coff=1&selm=aukkonen-FE5275.21093624062003%40shawnews.gv.shawcable.net&rnum=16 another which has some hints as to how it should be handled http://groups.google.com/groups?q=hyperthreading+dual+xeon+idle&start=10&hl=en&lr=&ie=UTF-8&c2coff=1&selm=u5tl1XD3BHA.2760%40tkmsftngp04&rnum=19 FWIW, I have anecdotal evidence that suggests that this is the case, on of my clients was seeing very large context switches with HTT turned on, and without it was much better. Dave On Sun, 2004-04-18 at 23:19, Tom Lane wrote: > >> What about hypterthreading does it still happen if HTT is turned off ? > > > The problem comes from keeping the caches synchronized between multiple > > physical CPUs. AFAICS enabling HTT wouldn't make it worse, because a > > hyperthreaded processor still only has one cache. > > Also, I forgot to say that the numbers I'm quoting *are* with HTT off. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 8: explain analyze is your friend > > > > !DSPAM:40834781158911062514350! > > -- Dave Cramer 519 939 0336 ICQ # 14675561