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 2586BD1DB96 for ; Thu, 22 Apr 2004 03:04:53 -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 94654-09 for ; Thu, 22 Apr 2004 03:04:43 -0300 (ADT) Received: from www.postgresql.com (www.postgresql.com [200.46.204.209]) by svr1.postgresql.org (Postfix) with ESMTP id 15BD5D1EB82 for ; Thu, 22 Apr 2004 03:02:32 -0300 (ADT) Received: from net2.micro-automation.com (net2.micro-automation.com [64.7.141.29]) by www.postgresql.com (Postfix) with SMTP id BAD7DCF64A3 for ; Thu, 22 Apr 2004 00:03:49 -0300 (ADT) Received: (qmail 9328 invoked from network); 22 Apr 2004 03:03:41 -0000 Received: from dcdsl.ebox.com (HELO ?192.168.1.36?) (davec@64.7.143.116) by net2.micro-automation.com with SMTP; 22 Apr 2004 03:03:41 -0000 Subject: Re: Wierd context-switching issue on Xeon patch for 7.4.1 From: Dave Cramer Reply-To: pg@fastcrypt.com To: Tom Lane Cc: Paul Tuckfield , Anjan Dave , Josh Berkus , Neil Conway , Dirk =?ISO-8859-1?Q?Lutzeb=E4ck?= , pgsql-performance@postgresql.org In-Reply-To: <18322.1082601330@sss.pgh.pa.us> References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509814A@vt-pe2550-001.vantage.vantage.com> <200404200959.52813.josh@agliodbs.com> <1082515263.1558.214.camel@localhost.localdomain> <78427208-93C0-11D8-BA67-000393BD6C3E@tuckfield.com> <1082574808.1558.243.camel@localhost.localdomain> <1082580588.13371.260.camel@localhost.localdomain> <18322.1082601330@sss.pgh.pa.us> Content-Type: text/plain Organization: Cramer Consulting Message-Id: <1082603201.1556.272.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 21 Apr 2004 23:06:41 -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-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200404/375 X-Sequence-Number: 6675 Yeah, I did some more testing myself, and actually get better numbers with increasing spins per delay to 1000, but my suspicion is that it is highly dependent on finding the right delay for the processor you are on. My hypothesis is that if you spin approximately the same or more time than the average time it takes to get finished with the shared resource then this should reduce cs. Certainly more ideas are required here. Dave On Wed, 2004-04-21 at 22:35, Tom Lane wrote: > Dave Cramer writes: > > diff -c -r1.16 s_lock.c > > *** backend/storage/lmgr/s_lock.c 8 Aug 2003 21:42:00 -0000 1.16 > > --- backend/storage/lmgr/s_lock.c 21 Apr 2004 20:27:34 -0000 > > *************** > > *** 76,82 **** > > * The select() delays are measured in centiseconds (0.01 sec) because 10 > > * msec is a common resolution limit at the OS level. > > */ > > ! #define SPINS_PER_DELAY 100 > > #define NUM_DELAYS 1000 > > #define MIN_DELAY_CSEC 1 > > #define MAX_DELAY_CSEC 100 > > --- 76,82 ---- > > * The select() delays are measured in centiseconds (0.01 sec) because 10 > > * msec is a common resolution limit at the OS level. > > */ > > ! #define SPINS_PER_DELAY 10 > > #define NUM_DELAYS 1000 > > #define MIN_DELAY_CSEC 1 > > #define MAX_DELAY_CSEC 100 > > > As far as I can tell, this does reduce the rate of semop's > significantly, but it does so by bringing the overall processing rate > to a crawl :-(. I see 97% CPU idle time when using this patch. > I believe what is happening is that the select() delay in s_lock.c is > being hit frequently because the spin loop isn't allowed to run long > enough to let the other processor get out of the spinlock. > > regards, tom lane > > > > !DSPAM:40872f7e21492906114513! > > -- Dave Cramer 519 939 0336 ICQ # 14675561