| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Robert Creager <robertc(at)spectralogic(dot)com> |
| Cc: | "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Need help identifying a periodic performance issue. |
| Date: | 2021-11-16 22:51:46 |
| Message-ID: | CA+hUKGLv6GmiCmWX1fkftJG0QLEM9uFHUUWFdgNLjOPbZyEunQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, Nov 17, 2021 at 11:40 AM Robert Creager
<robertc(at)spectralogic(dot)com> wrote:
> Presuming this is the type of output you are expecting:
>
> CPU ID FUNCTION:NAME
> 0 58709 :tick-10s
>
>
> postgres`AtEOXact_LargeObject+0x11
> postgres`CommitTransaction+0x127
> postgres`CommitTransactionCommand+0xf2
> postgres`PostgresMain+0x1fef
> postgres`process_startup_packet_die
> postgres`0x73055b
> postgres`PostmasterMain+0xf36
> postgres`0x697837
> postgres`_start+0x100
> `0x80095f008
> 1
It's the right output format, but isn't /pid == '$PID'/ only going to
match one single process called "postgres"? Maybe /execname ==
"postgres"/ to catch them all? Hopefully it'll be obvious what's
going on from an outlier stack with a high sample count. Can also be
useful to convert the output to flamegraph format if CPU time is
distributed over many distinct stacks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2021-11-16 22:52:53 | Re: Need help identifying a periodic performance issue. |
| Previous Message | Robert Creager | 2021-11-16 22:40:43 | Re: Need help identifying a periodic performance issue. |