pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: pg@fastcrypt.com
Cc: Josh Berkus <josh@agliodbs.com>
Cc: Paul Tuckfield <paul@tuckfield.com>
Cc: Anjan Dave <adave@vantage.com>
Cc: Neil Conway <neilc@samurai.com>
Cc: Dirk Lutzebäck <lutzeb@aeccom.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Wierd context-switching issue on Xeon patch for 7.4.1
Date: Thu, 22 Apr 2004 00:23:24 -0400
Message-ID: <19596.1082607804@sss.pgh.pa.us> (raw)
In-Reply-To: <1082603927.1558.279.camel@localhost.localdomain>
References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509814A@vt-pe2550-001.vantage.vantage.com>
	<1082580588.13371.260.camel@localhost.localdomain>
	<18322.1082601330@sss.pgh.pa.us>
	<200404211953.24898.josh@agliodbs.com>
	<1082603927.1558.279.camel@localhost.localdomain>

Dave Cramer <pg@fastcrypt.com> writes:
> I tried increasing the NUM_SPINS to 1000 and it works better.

Doesn't surprise me.  The value of 100 is about right on the assumption
that the spinlock instruction per se is not too much more expensive than
any other instruction.  What I was seeing from oprofile suggested that
the spinlock instruction cost about 100x more than an ordinary
instruction :-( ... so maybe 200 or so would be good on a Xeon.

> This is certainly heading in the right direction ? Although it looks
> like it is highly dependent on the system you are running on.

Yeah.  I don't know a reasonable way to tune this number automatically
for particular systems ... but at the very least we'd need to find a way
to distinguish uniprocessor from multiprocessor, because on a
uniprocessor the optimal value is surely 1.

			regards, tom lane



view thread (22+ messages)  latest in thread

Message-ID: <19596.1082607804@sss.pgh.pa.us>
Permalink:  ../19596.1082607804@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/19596.1082607804@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, pg@fastcrypt.com, josh@agliodbs.com, paul@tuckfield.com, adave@vantage.com, neilc@samurai.com, lutzeb@aeccom.com
  Subject: Re: Wierd context-switching issue on Xeon patch for 7.4.1
  In-Reply-To: <19596.1082607804@sss.pgh.pa.us>

* 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