pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dave Cramer <pg@fastcrypt.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Wierd context-switching issue on Xeon patch for 7.4.1
Date: Tue, 27 Apr 2004 14:27:33 -0400
Message-ID: <1083090452.14759.224.camel@localhost.localdomain> (raw)
In-Reply-To: <200404271105.00395.josh@agliodbs.com>
References: <4BAFBB6B9CC46F41B2AD7D9F4BBAF78509814A@vt-pe2550-001.vantage.vantage.com>
	<200404261703.25631.josh@agliodbs.com>
	<1083024960.14759.166.camel@localhost.localdomain>
	<200404271105.00395.josh@agliodbs.com>

Josh,

I think you can safely increase by orders of magnitude here, instead of
by +100, my wild ass guess is that the sweet spot is the spin time
should be approximately the time it takes to consume the resource. So if
you have a really fast machine then the spin count should be higher. 

Also you have to take into consideration your memory bus speed, with the
pause instruction inserted in the loop the timing is now dependent on
memory speed.

But... you need a baseline first.

Dave
On Tue, 2004-04-27 at 14:05, Josh Berkus wrote:
> Dave,
> 
> > Are you testing this with Tom's code, you need to do a baseline
> > measurement with 10 and then increase it, you will still get lots of cs,
> > but it will be less.
> 
> No, that was just a test of 1000 straight up.    Tom outlined a method, but I 
> didn't see any code that would help me find a better level, other than just 
> trying each +100 increase one at a time.   This would take days of testing 
> ...
-- 
Dave Cramer
519 939 0336
ICQ # 14675561




view thread (22+ messages)  latest in thread

Message-ID: <1083090452.14759.224.camel@localhost.localdomain>
Permalink:  ../1083090452.14759.224.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1083090452.14759.224.camel@localhost.localdomain

 · 

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: pg@fastcrypt.com, josh@agliodbs.com, tgl@sss.pgh.pa.us
  Subject: Re: Wierd context-switching issue on Xeon patch for 7.4.1
  In-Reply-To: <1083090452.14759.224.camel@localhost.localdomain>

* 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