pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndQuadrant.com>
To: Matthew Wakeling <matthew@flymine.org>
Cc: Jignesh K. Shah <J.K.Shah@Sun.COM>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Proposal of tunable fix for scalability of 8.4
Date: Wed, 18 Mar 2009 23:07:34 +0000
Message-ID: <1237417654.3953.320.camel@ebony.2ndQuadrant> (raw)
In-Reply-To: <alpine.DEB.2.00.0903181346320.21772@aragorn.flymine.org>
References: <alpine.GSO.2.01.0903121613270.1925@westnet.com>
	<C5DED7A7.33B2%scott@richrelevance.com>
	<603c8f070903121829r31cf1472ha9876e5c480a542e@mail.gmail.com>
	<12292.1236964604@sss.pgh.pa.us>
	<49BB699D.1070809@enterprisedb.com>
	<alpine.DEB.2.00.0903161543590.21772@aragorn.flymine.org>
	<1237362833.3953.186.camel@ebony.2ndQuadrant>
	<alpine.DEB.2.00.0903181141000.21772@aragorn.flymine.org>
	<1237378009.3953.303.camel@ebony.2ndQuadrant>
	<49C0F946.8080008@sun.com>
	<alpine.DEB.2.00.0903181346320.21772@aragorn.flymine.org>


On Wed, 2009-03-18 at 13:49 +0000, Matthew Wakeling wrote:
> On Wed, 18 Mar 2009, Jignesh K. Shah wrote:
> > I thought about that.. Except without putting a restriction a huge queue will cause lot of time spent in manipulating the lock
> > list every time. One more thing will be to maintain two list shared and exclusive and round robin through them for every time you
> > access the list so manipulation is low.. But the best thing is to allow flexibility to change the algorithm since some workloads
> > may work fine with one and others will NOT. The flexibility then allows to tinker for those already reaching the limits.
> 
> Yeah, having two separate queues is the obvious way of doing this. It 
> would make most operations really trivial. Just wake everything in the 
> shared queue at once, and you can throw it away wholesale and allocate a 
> new queue. It avoids a whole lot of queue manipulation.

Yes, that sounds good.

-- 
 Simon Riggs           www.2ndQuadrant.com
 PostgreSQL Training, Services and Support




view thread (119+ messages)  latest in thread

Message-ID: <1237417654.3953.320.camel@ebony.2ndQuadrant>
Permalink:  ../1237417654.3953.320.camel@ebony.2ndQuadrant/
Also on:    postgresql.org/message-id/1237417654.3953.320.camel@ebony.2ndQuadrant

 · 

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: simon@2ndQuadrant.com, matthew@flymine.org, J.K.Shah@Sun.COM
  Subject: Re: Proposal of tunable fix for scalability of 8.4
  In-Reply-To: <1237417654.3953.320.camel@ebony.2ndQuadrant>

* 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