Skip site navigation (1) Skip section navigation (2)

Re: User concurrency thresholding: where do I look?

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: "Jignesh K(dot) Shah" <J(dot)K(dot)Shah(at)Sun(dot)COM>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: User concurrency thresholding: where do I look?
Date: 2007-07-27 08:58:05
Message-ID: 20070727085805.GF2550@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-performance
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.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

pgsql-performance by date

Next:From: Simon RiggsDate: 2007-07-27 09:15:13
Subject: Re: User concurrency thresholding: where do I look?
Previous:From: Mark KirkwoodDate: 2007-07-27 00:48:36
Subject: Re: disk filling up

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group