Re: Dynamic LWLock tracing via pg_stat_lwlock (proof of concept)

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Dynamic LWLock tracing via pg_stat_lwlock (proof of concept)
Дата
Msg-id CA+TgmoaDqSvbUB6pOVNUZjqG32W72TAO8nJzzsZ=dMG2Un8q2Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Dynamic LWLock tracing via pg_stat_lwlock (proof of concept)  (Andres Freund <andres@2ndquadrant.com>)
Список pgsql-hackers
On Tue, Oct 7, 2014 at 10:51 AM, Andres Freund <andres@2ndquadrant.com> wrote:
> On 2014-10-07 10:45:24 -0400, Robert Haas wrote:
>> > It's not like it'd be significantly different today - in a read mostly
>> > workload that's bottlenecked on ProcArrayLock you'll not see many
>> > waits. There you'd have to count the total number of spinlocks cycles to
>> > measure anything interesting.
>>
>> Hmm, really?  I've never had to do that to find bottlenecks.
>
> How did you diagnose procarray contention in a readonly workload
> otherwise, without using perf?

spindelays.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: lwlock contention with SSI
Следующее
От: Kevin Grittner
Дата:
Сообщение: Re: lwlock contention with SSI