pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: pg@fastcrypt.com
Subject: Context Switching issue: Spinlock doesn't fix.
Date: Wed, 2 Jun 2004 12:25:25 -0700
Message-ID: <200406021225.25463.josh@agliodbs.com> (raw)

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




view thread (3+ messages)  latest in thread

Message-ID: <200406021225.25463.josh@agliodbs.com>
Permalink:  ../200406021225.25463.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200406021225.25463.josh@agliodbs.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: josh@agliodbs.com, pg@fastcrypt.com
  Subject: Re: Context Switching issue: Spinlock doesn't fix.
  In-Reply-To: <200406021225.25463.josh@agliodbs.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox