From: | Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> |
---|---|
To: | pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #12071: Stat collector went crasy (50MB/s constant writes) |
Date: | 2014-11-26 18:48:30 |
Message-ID: | CAK-MWwQJF+EM5f_47r5wLpr6_2FBYNFeKKAD-DPP3JtzuAM15Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Wed, Nov 26, 2014 at 9:08 PM, Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> wrote:
>
> On one of my servers stat collector went crasy on idle system.
>> It constantly write around 50MB/s on idle database (no activity at all).
>>
>
OK there are results of some low-level gdb kung-fu:
problem point is:
/*
* Write the stats file if a new request has arrived that is not
* satisfied by existing file.
*/
if (last_statwrite < last_statrequest)
pgstat_write_statsfile(false);
on some loop iteration difference between last_statrequest and
last_statwrite is around 23000-29000 (e.g. 20-30ms).
Hm may be there some clock drift between CPU cores?
Kind Regards,
Maksym
--
Maxim Boguk
Senior Postgresql DBA
http://www.postgresql-consulting.ru/ <http://www.postgresql-consulting.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2014-11-26 20:06:37 | Re: BUG #12071: Stat collector went crasy (50MB/s constant writes) |
Previous Message | Maxim Boguk | 2014-11-26 18:08:43 | Re: BUG #12071: Stat collector went crasy (50MB/s constant writes) |
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Shulgin | 2014-11-26 18:52:46 | Re: [PATCH] add ssl_protocols configuration option |
Previous Message | Alvaro Herrera | 2014-11-26 18:19:36 | Re: no test programs in contrib |