MIME-Version: 1.0
In-Reply-To: 
 <CANYYVq+vJ+8ZUm-jGVXd=Y4vPBKhd0R72nNtY-3tFYJ81YWPwQ@mail.gmail.com>
References: 
 <CANYYVq+vJ+8ZUm-jGVXd=Y4vPBKhd0R72nNtY-3tFYJ81YWPwQ@mail.gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
Date: Wed, 2 Mar 2016 16:31:15 +0100
Message-ID: 
 <CAFj8pRBkF6qq=A7GnyNNvP6vWzb=WdtcEQpUUyL+12o_Ccx2aA@mail.gmail.com>
Subject: Re: [PERFORM] autovacuum disk IO
To: Artem Tomyuk <admin@leboutique.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>,
	"pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Content-Type: multipart/alternative; boundary=94eb2c034e8cee3d46052d129429
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

--94eb2c034e8cee3d46052d129429
Content-Type: text/plain; charset=UTF-8

Hi

2016-03-02 16:25 GMT+01:00 Artem Tomyuk <admin@leboutique.com>:

> Hi.
>
> I've noticed that autovac. process worked more than 10 minutes, during
> this zabbix logged more than 90% IO disk utilization on db volume....
>
> ===========>29237   2016-03-02 15:17:23 EET 00000 [24-1]LOG:  automatic vacuum of table "lb_upr.public._reference32": index scans: 1
> 	pages: 0 removed, 263307 remain
> 	tuples: 298 removed, 1944753 remain, 0 are dead but not yet removable
> 	buffer usage: 67814 hits, 265465 misses, 15647 dirtied
> 	avg read rate: 3.183 MB/s, avg write rate: 0.188 MB/s
> 	*system usage: CPU 5.34s/6.27u sec elapsed 651.57 sec*
>
> Is it possible to log autovac. io impact during it execution?
> Is there any way to limit or "nice" autovac. process?
>
> Thanks to all for any help.
>
>
maybe offtopic - there is known problem of Zabbix. Any limits for vacuum
are usually way to hell.

But more times the partitioning helps to Zabbix

https://www.zabbix.org/wiki/Higher_performant_partitioning_in_PostgreSQL

Regards

Pavel

--94eb2c034e8cee3d46052d129429
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi<br><div><div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">2016-03-02 16:25 GMT+01:00 Artem Tomyuk <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:admin@leboutique.com" target=3D"_blank">admin@leboutique.co=
m</a>&gt;</span>:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div=
 dir=3D"ltr">Hi.=C2=A0<div><br></div><div>I&#39;ve noticed that autovac. pr=
ocess worked more than 10 minutes, during this zabbix logged more than 90% =
IO disk utilization on db volume....</div><div><br></div><div><pre style=3D=
"color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D&gt;29237   2016-03-02 15:17:23 EET 00000 [24-1]LOG:  =
automatic vacuum of table &quot;lb_upr.public._reference32&quot;: index sca=
ns: 1
	pages: 0 removed, 263307 remain
	tuples: 298 removed, 1944753 remain, 0 are dead but not yet removable
	buffer usage: 67814 hits, 265465 misses, 15647 dirtied
	avg read rate: 3.183 MB/s, avg write rate: 0.188 MB/s
	<b>system usage: CPU 5.34s/6.27u sec elapsed 651.57 sec</b></pre>Is it pos=
sible to log autovac. io impact during it execution?</div><div>Is there any=
 way to limit or &quot;nice&quot; autovac. process?</div><div><br></div><di=
v>Thanks to all for any help.=C2=A0</div><div><br></div></div>
</blockquote></div><br></div><div class=3D"gmail_extra">maybe offtopic - th=
ere is known problem of Zabbix. Any limits for vacuum are usually way to he=
ll.<br><br></div><div class=3D"gmail_extra">But more times the partitioning=
 helps to Zabbix<br><br><a href=3D"https://www.zabbix.org/wiki/Higher_perfo=
rmant_partitioning_in_PostgreSQL">https://www.zabbix.org/wiki/Higher_perfor=
mant_partitioning_in_PostgreSQL</a><br><br></div><div class=3D"gmail_extra"=
>Regards<br><br></div><div class=3D"gmail_extra">Pavel<br></div></div></div=
>

--94eb2c034e8cee3d46052d129429--