Re: [GENERAL] BDR, wal sender, high system cpu, mutex_lock_common - Mailing list pgsql-general

From Craig Ringer
Subject Re: [GENERAL] BDR, wal sender, high system cpu, mutex_lock_common
Date
Msg-id CAMsr+YEBRuNgwv9yjOT5St2hWVhMZMSomGxtdREX6=nqNFv9Ew@mail.gmail.com
Whole thread Raw
In response to [GENERAL] BDR, wal sender, high system cpu, mutex_lock_common  (milist ujang <ujang.milist@gmail.com>)
Responses Re: [GENERAL] BDR, wal sender, high system cpu, mutex_lock_common  (milist ujang <ujang.milist@gmail.com>)
List pgsql-general
On 3 October 2017 at 19:45, milist ujang <ujang.milist@gmail.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

pgsql-general by date:

Previous
From: milist ujang
Date:
Subject: [GENERAL] BDR, wal sender, high system cpu, mutex_lock_common
Next
From: milist ujang
Date:
Subject: Re: [GENERAL] BDR, wal sender, high system cpu, mutex_lock_common