X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id A649FD1B441 for ; Tue, 25 Nov 2003 23:48:27 +0000 (GMT) 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 56083-04 for ; Tue, 25 Nov 2003 19:47:57 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 7CF28D1B43B for ; Tue, 25 Nov 2003 19:47:55 -0400 (AST) Received: from [66.219.92.2] (HELO temoku) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3978264; Tue, 25 Nov 2003 15:48:45 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Tom Lane Subject: Re: Wierd context-switching issue on Xeon Date: Tue, 25 Nov 2003 15:37:42 -0800 User-Agent: KMail/1.4.3 Cc: pgsql-performance@postgresql.org References: <200311251419.36771.josh@agliodbs.com> <9470.1069803647@sss.pgh.pa.us> In-Reply-To: <9470.1069803647@sss.pgh.pa.us> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200311251537.42527.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/261 X-Sequence-Number: 4821 Tom, > Strictly a WAG ... but what this sounds like to me is disastrously bad > behavior of the spinlock code under heavy contention. We thought we'd > fixed the spinlock code for SMP machines awhile ago, but maybe > hyperthreading opens some new vistas for misbehavior ... Yeah, I thought of that based on the discussion on -Hackers. But we tried= =20 turning off hyperthreading, with no change in behavior. > If you can't try 7.4, or want to gather more data first, it would be > good to try to confirm or disprove the theory that the context switches > are coming from spinlock delays. If they are, they'd be coming from the > select() calls in s_lock() in s_lock.c. Can you strace or something to > see what kernel calls the context switches occur on? Might be worth it ... will suggest that. Will also try 7.4. --=20 -Josh Berkus Aglio Database Solutions San Francisco