pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Jignesh K. Shah <J.K.Shah@Sun.COM>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: User concurrency thresholding: where do I look?
Date: Fri, 27 Jul 2007 10:15:13 +0100
Message-ID: <1185527713.4191.20.camel@ebony.site> (raw)
In-Reply-To: <20070727085805.GF2550@alvh.no-ip.org>
References: <1545.1185214760@sss.pgh.pa.us>
	<46A7D5AD.9000706@sun.com>
	<13162.1185405865@sss.pgh.pa.us>
	<46A8AFDF.3050804@sun.com>
	<26825.1185460816@sss.pgh.pa.us>
	<46A8BD62.2080904@sun.com>
	<1185465076.4190.87.camel@ebony.site>
	<46A8F9AA.4040507@sun.com>
	<1185480291.5510.22.camel@ebony.site>
	<46A90F83.8050401@sun.com>
	<20070727085805.GF2550@alvh.no-ip.org>

On Fri, 2007-07-27 at 04:58 -0400, Alvaro Herrera wrote:
> Jignesh K. Shah wrote:
> 
> > Top Wait time   seems to come from the following code path for 
> > ProcArrayLock:
> >
> >             Lock Id            Mode           Count
> >       ProcArrayLock       Exclusive              21
> >
> >             Lock Id   Combined Time (ns)
> >       ProcArrayLock           5255937500
> >
> >             Lock Id   Combined Time (ns)
> >
> >
> >              postgres`LWLockAcquire+0x1f0
> >              postgres`CommitTransaction+0x104
> 
> Yeah, ProcArrayLock is pretty contended.  I think it would be kinda neat
> if we could split it up in partitions.  This lock is quite particular
> though.

Maybe, if we did we should set the partitions according to numbers of
users, so lower numbers of users are all in one partition.

-- 
  Simon Riggs
  EnterpriseDB  http://www.enterprisedb.com




view thread (58+ messages)  latest in thread

Message-ID: <1185527713.4191.20.camel@ebony.site>
Permalink:  ../1185527713.4191.20.camel@ebony.site/
Also on:    postgresql.org/message-id/1185527713.4191.20.camel@ebony.site

 · 

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, alvherre@commandprompt.com, J.K.Shah@Sun.COM, tgl@sss.pgh.pa.us, josh@agliodbs.com
  Subject: Re: User concurrency thresholding: where do I look?
  In-Reply-To: <1185527713.4191.20.camel@ebony.site>

* 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