Re: User concurrency thresholding: where do I look?
| От | Simon Riggs |
|---|---|
| Тема | Re: User concurrency thresholding: where do I look? |
| Дата | |
| Msg-id | 1185527713.4191.20.camel@ebony.site обсуждение исходный текст |
| Ответ на | Re: User concurrency thresholding: where do I look? (Alvaro Herrera <alvherre@commandprompt.com>) |
| Список | pgsql-performance |
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
В списке pgsql-performance по дате отправления: