Hi 2016-03-02 16:25 GMT+01:00 Artem Tomyuk <ad...@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
