| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Martin Moore <martin(dot)moore(at)avbrief(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Replication causing publisher node to use excessive cpu over time |
| Date: | 2017-12-04 12:40:54 |
| Message-ID: | CAB7nPqRWPmA+xs2FPc5Jpy4ZX3iAzirWznA69F_ZcROEoGa9rA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Dec 4, 2017 at 9:03 PM, Martin Moore <martin(dot)moore(at)avbrief(dot)com> wrote:
> After a few days, it’s noticeable that the Postgres on the publisher node is constantly using a lot of cpu (26% today) and having a big impact on the system performance even when doing very little. Logging on to the subscriber and removing the subscription sees this value drop to an expect small value.
When debugging such issues, it is critical to know where the resources
are spent, and you are giving no information that can help in
understanding where CPU cycles are spent. You can do such measurements
by using perf for example.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Moore | 2017-12-04 13:00:16 | Re: Replication causing publisher node to use excessive cpu over time |
| Previous Message | Jakub Glapa | 2017-12-04 12:18:38 | Re: ERROR: too many dynamic shared memory segments |