| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | milist ujang <ujang(dot)milist(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: BDR, wal sender, high system cpu, mutex_lock_common |
| Date: | 2017-10-12 02:25:43 |
| Message-ID: | CAMsr+YFVkhHDXXdN6Yyg+UfZFRCUjNNRb_CHoC=dYL_-FaF0CQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 4 October 2017 at 00:21, milist ujang <ujang(dot)milist(at)gmail(dot)com> wrote:
> On Tue, Oct 3, 2017 at 8:49 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
>>
>>
>> Can you get stacks please?
>>
>> Use -g
>
>
> # Events: 2K cpu-clock
> #
> # Overhead Command Shared Object Symbol
> # ........ ........ ................. ............................
> #
> 86.96% postgres [kernel.kallsyms] [k] __mutex_lock_common.isra.5
> |
> --- __mutex_lock_common.isra.5
> read
Unfortunately it looks like you're using a postgres built with
-fomit-frame-pointers (the default) on x64, with an older perf not
built with libunwind. This produces useless stacks.
You may need to recompile with -fno-omit-frame-pointer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-10-12 03:03:50 | Re: BDR, wal sender, high system cpu, mutex_lock_common |
| Previous Message | David Rowley | 2017-10-11 22:12:01 | Re: Equivalence Classes when using IN |