Re: [GENERAL] BDR, wal sender, high system cpu, mutex_lock_common
| От | Craig Ringer |
|---|---|
| Тема | Re: [GENERAL] BDR, wal sender, high system cpu, mutex_lock_common |
| Дата | |
| Msg-id | CAMsr+YFVkhHDXXdN6Yyg+UfZFRCUjNNRb_CHoC=dYL_-FaF0CQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [GENERAL] BDR, wal sender, high system cpu, mutex_lock_common (milist ujang <ujang.milist@gmail.com>) |
| Ответы |
Re: [GENERAL] BDR, wal sender, high system cpu, mutex_lock_common
|
| Список | pgsql-general |
On 4 October 2017 at 00:21, milist ujang <ujang.milist@gmail.com> wrote: > On Tue, Oct 3, 2017 at 8:49 PM, Craig Ringer <craig@2ndquadrant.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 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
В списке pgsql-general по дате отправления: