Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ab8eh-0005QP-3N for pgsql-admin@arkaria.postgresql.org; Wed, 02 Mar 2016 15:25:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ab8eg-0007BK-Hu for pgsql-admin@arkaria.postgresql.org; Wed, 02 Mar 2016 15:25:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ab8ef-00079X-C1 for pgsql-admin@postgresql.org; Wed, 02 Mar 2016 15:25:37 +0000 Received: from mail-wm0-x234.google.com ([2a00:1450:400c:c09::234]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ab8eY-0000c2-N3 for pgsql-admin@postgresql.org; Wed, 02 Mar 2016 15:25:36 +0000 Received: by mail-wm0-x234.google.com with SMTP id n186so91149207wmn.1 for ; Wed, 02 Mar 2016 07:25:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leboutique.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=A561eyv3pSfR7RGs/MdEk+Nxli59l85CUABWzE+tzzs=; b=GtQcMrVAB8WkT8QtcxJ3NeQU8qqwaN+GP+PiQoAQAU3XqKU+AXvYoEEgov978oPGsR B5choX3lGM14tI/mJAoRknspNFrxKyMeAbBZCa0vt0gxtC0ggKta/hJOdz9kkuWplL4n aqFx6FJiGc3tsOZXNafx0vi1N8pQgOFeNmT6w= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=A561eyv3pSfR7RGs/MdEk+Nxli59l85CUABWzE+tzzs=; b=DvryV7psPdJgMnCQsEGBrz3MMsptMH0it4YA1pYpkZjYVLIKsAaFCiXeCcqCB+ovv6 DNzTymSLuW6fzVDsJvCQsqnxJHOOxfUPSX7osxVoLpX8IfdDWvL+vHpahmjb7IEleiFQ F1AFTeDQ/pI7yBrIHpGags6DJFey0ZJ5ENQHbKGl4s5nyAUh5avLBkH5D1Q97Jc+Cu/q /rgDA8KLPUG4dOHVvbN3dPHm++6kON39UJKTkD4K+WNFJ0NX3t6XgpoQ282ic6HDrhKM 5edxdtRKUoC0rs4JI0ZG0XVG7jDV//t2m4RMXKnNigXIeVvardwIddQqlWJWrxzgd1uE ocpA== X-Gm-Message-State: AD7BkJKix5DGuuh8DvC6f5G/c4XqGY2a8SXzx4eNKQnLkq/XEzEzqXCHGyHDBb+v7VRRcFUqarYBh2EZdxEe1CIX X-Received: by 10.28.104.87 with SMTP id d84mr543657wmc.56.1456932329480; Wed, 02 Mar 2016 07:25:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.27.189.213 with HTTP; Wed, 2 Mar 2016 07:25:10 -0800 (PST) From: Artem Tomyuk Date: Wed, 2 Mar 2016 17:25:10 +0200 Message-ID: Subject: autovacuum disk IO To: pgsql-admin@postgresql.org, pgsql-performance@postgresql.org Content-Type: multipart/alternative; boundary=001a114b2f32f6439f052d127d99 X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --001a114b2f32f6439f052d127d99 Content-Type: text/plain; charset=UTF-8 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. --001a114b2f32f6439f052d127d99 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi.=C2=A0

I've noticed that autovac= . process worked more than 10 minutes, during this zabbix logged more than = 90% IO disk utilization on db volume....

=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D>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 pos= sible to log autovac. io impact during it execution?
Is there any= way to limit or "nice" autovac. process?

Thanks to all for any help.=C2=A0

--001a114b2f32f6439f052d127d99--