| From: | Victor Yegorov <vyegorov(at)gmail(dot)com> |
|---|---|
| To: | pinker <pinker(at)onet(dot)eu> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: core system is getting unresponsive because over 300 cpu load |
| Date: | 2017-10-10 21:01:48 |
| Message-ID: | CAGnEboj64WH_zGVmiN=UE9ekLc1d4Z8MbSMrS=8cXTt3qOsBsQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2017-10-10 23:40 GMT+03:00 pinker <pinker(at)onet(dot)eu>:
> We've got problem with a very serious repetitive incident on our core
> system. Namely, cpu load spikes to 300-400 and the whole db becomes
> unresponsive. From db point of view nothing special is happening, memory
> looks fine, disks io's are ok and the only problem is huge cpu load. Kernel
> parameters that are increasing with load are always the same:
>
Can you provide output of `iostat -myx 10` at the “peak” moments, please?
Also, it'd be good to look in more detailed bgwriter/checkpointer stats.
You can find more details in this post: http://blog.postgresql-
consulting.com/2017/03/deep-dive-into-postgres-stats_27.html
(You might want to reset 'shared' stats here.)
--
Victor Yegorov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2017-10-10 21:12:13 | Re: core system is getting unresponsive because over 300 cpu load |
| Previous Message | pinker | 2017-10-10 20:51:21 | Re: core system is getting unresponsive because over 300 cpu load |