X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 65561D1B1DC for ; Wed, 2 Jun 2004 16:25:17 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 74852-03 for ; Wed, 2 Jun 2004 19:25:18 +0000 (GMT) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 89B20D1B1D0 for ; Wed, 2 Jun 2004 16:25:15 -0300 (ADT) Received: from [64.81.245.111] (HELO 192.168.1.102) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 5257425; Wed, 02 Jun 2004 12:26:50 -0700 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: pgsql-performance@postgresql.org Subject: Context Switching issue: Spinlock doesn't fix. Date: Wed, 2 Jun 2004 12:25:25 -0700 User-Agent: KMail/1.5.4 Cc: pg@fastcrypt.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200406021225.25463.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200406/14 X-Sequence-Number: 7072 Folks, I've been testing varying SPINS_PER_DELAY in a client's installation of PostgreSQL against a copy of a production database, to test varying this statistic as a way of fixing the issue. It does not seem to work. I've tested all of the following graduated levels: 100 (the original) 250 500 1000 2000 5000 10000 20000 30000 50000 None of these quantities seem to make any difference at all in the number of context switches -- neither down nor up. Seems to me like this is a dead end. Does anyone have test results that show otherwise? -- -Josh Berkus Aglio Database Solutions San Francisco