| 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-03 13:49:55 |
| Message-ID: | CAMsr+YEBRuNgwv9yjOT5St2hWVhMZMSomGxtdREX6=nqNFv9Ew@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 3 October 2017 at 19:45, milist ujang <ujang(dot)milist(at)gmail(dot)com> wrote:
> Hi all,
>
> I've an environment 9.4 + bdr:
> PostgreSQL 9.4.4
>
You're on a pretty old postgres-bdr. Update. You're missing a lot of fixes
from mainline.
> This is consolidation databases, in this machine there are around 250+ wal
> sender processes.
>
Not a great use case for BDR.
Consider pglogical.
>
> finally get which processes (wal senders) that are using mutexes:
>
> perf top -e task-clock -p 55382
>
>
Can you get stacks please?
Use -g
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | milist ujang | 2017-10-03 16:21:56 | Re: BDR, wal sender, high system cpu, mutex_lock_common |
| Previous Message | milist ujang | 2017-10-03 11:45:17 | BDR, wal sender, high system cpu, mutex_lock_common |