From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Additional LWLOCK_STATS statistics |
Date: | 2015-09-15 19:11:18 |
Message-ID: | CA+TgmoYvgL7rA6jBzn60FUeHhb5TH2xu2m9JKPiXFqbZ5Dyi7w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Sep 15, 2015 at 10:27 AM, Jesper Pedersen
<jesper(dot)pedersen(at)redhat(dot)com> wrote:
> Hi,
>
> I have been using the attached patch to look at how each LWLock relates to
> each other in various types of runs.
>
> The patch adds the following fields to a LWLOCK_STATS build:
>
> sh_acquire_max (int):
>
> The maximum shared locks in series for the lock
>
> ex_acquire_max (int):
>
> The maximum exclusive locks in series for the lock
>
> max_waiters (int):
>
> The maximum numbers of waiters
>
> Also attached is a sample report using FlameGraphs from a pgbench run using
>
> -c 80 -j 80 -T 300
>
> See README for additional details.
>
> If there is an interest I'll add the patch to the next CommitFest.
>
> Thanks for considering, and any feedback is most welcomed.
Seems neat, but I can't understand how to read the flame graphs.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Brightwell | 2015-09-15 19:18:21 | Re: row_security GUC, BYPASSRLS |
Previous Message | Robert Haas | 2015-09-15 19:06:31 | Re: [PATCH] Refactoring of LWLock tranches |