From: | Tomas Vondra <tv(at)fuzzy(dot)cz> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #12071: Stat collector went crasy (50MB/s constant writes) |
Date: | 2014-11-26 21:50:55 |
Message-ID: | 54764B3F.5080702@fuzzy.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On 26.11.2014 22:19, Maxim Boguk wrote:
>
> No active autovacuum processes visible.
> Now just interesting calculation:
> autovacuum_naptime = 1 second (customized value from production)
> active databases - 9...
> Suspiciously close to 1/10 second.
> Testing: increase autovacuum_naptime to
> 10second - two writes per second.
> 100second - only two writes every 10 second.
>
> So yes, pgstat_send_inquiry definitely issued by autovacuum launcher.
> Now question why EVERY pgstat_send_inquiry request from autovacuum leads
> to the 1-2 full pgstat.stat rewrite on idle server?
Well, I think this explains it.
The autovacuum starts a worker for a particular database every
(naptime/ndatabases), so if you have naptime 1 second and 10 databases,
it will start a worker every 100 ms. And that's over the 10ms limit, so
every worker will force write of the statfile. And it explains the 50
MB/s writes.
Why have you set it to 1 second? The default is 1 minute, which is much
saner value.
I'm not sure why this was not happening before, though ...
Tomas
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2014-11-26 21:53:58 | Re: BUG #12071: Stat collector went crasy (50MB/s constant writes) |
Previous Message | Maxim Boguk | 2014-11-26 21:36:23 | Re: BUG #12071: Stat collector went crasy (50MB/s constant writes) |
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2014-11-26 21:53:58 | Re: BUG #12071: Stat collector went crasy (50MB/s constant writes) |
Previous Message | Stephen Frost | 2014-11-26 21:45:53 | Re: bug in json_to_record with arrays |