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

Re: User concurrency thresholding: where do I look?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jignesh K(dot) Shah" <J(dot)K(dot)Shah(at)Sun(dot)COM>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-performance(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Subject: Re: User concurrency thresholding: where do I look?
Date: 2007-07-26 15:42:48
Message-ID: 27577.1185464568@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
"Jignesh K. Shah" <J(dot)K(dot)Shah(at)Sun(dot)COM> writes:
> For  600-850 Users: that potential mislabeled CheckPointStartLock  or 
> LockID==12 comes from various sources where the top source (while system 
> is still doing great) comes from:

>               postgres`LWLockAcquire+0x1c8
>               postgres`SimpleLruReadPage_ReadOnly+0xc
>               postgres`TransactionIdGetStatus+0x14

That path would be taking CLogControlLock ... so you're off by at least
one.  Compare the script to src/include/storage/lwlock.h.

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: Simon RiggsDate: 2007-07-26 15:51:16
Subject: Re: User concurrency thresholding: where do I look?
Previous:From: Jignesh K. ShahDate: 2007-07-26 15:27:30
Subject: Re: User concurrency thresholding: where do I look?

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