Re: BUG #12071: Stat collector went crasy (50MB/s constant writes) - Mailing list pgsql-bugs

From Maxim Boguk
Subject Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)
Date
Msg-id CAK-MWwQJF+EM5f_47r5wLpr6_2FBYNFeKKAD-DPP3JtzuAM15Q@mail.gmail.com
Whole thread Raw
In response to Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)  (Maxim Boguk <maxim.boguk@gmail.com>)
Responses Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)  (Tomas Vondra <tv@fuzzy.cz>)
Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)  (Maxim Boguk <maxim.boguk@gmail.com>)
List pgsql-bugs
On Wed, Nov 26, 2014 at 9:08 PM, Maxim Boguk <maxim.boguk@gmail.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/>

pgsql-bugs by date:

Previous
From: Maxim Boguk
Date:
Subject: Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)
Next
From: Tomas Vondra
Date:
Subject: Re: BUG #12071: Stat collector went crasy (50MB/s constant writes)