Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e45ZO-0006j8-KG for pgsql-performance@arkaria.postgresql.org; Mon, 16 Oct 2017 13:36:38 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e45ZN-00068L-PM for pgsql-performance@arkaria.postgresql.org; Mon, 16 Oct 2017 13:36:37 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e45Xb-0002yI-DC for pgsql-performance@postgresql.org; Mon, 16 Oct 2017 13:34:47 +0000 Received: from mail-wm0-x22a.google.com ([2a00:1450:400c:c09::22a]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1e45XU-0004zE-4z for pgsql-performance@postgresql.org; Mon, 16 Oct 2017 13:34:46 +0000 Received: by mail-wm0-x22a.google.com with SMTP id m72so5105710wmc.0 for ; Mon, 16 Oct 2017 06:34:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=mI/WBHaF62dkGQkIY6wgY3MU1lGRGBbq7f4d7H8A2VM=; b=bRWtqweo5X6faoe2CZOpksIkLt67KqfQLe+1x9wqgbCAHh33a/VHKWZGvFroL8hOAX e+WMCnKMU+48XiAY9/zXTUTV9Snj4xG8L+Sgnx+gmWebOp6oHQxLDQME4q3A9Xsh1vSN KKTqxGAsaHCKqonhw4ObqYAUQ+hkhNkQiT4y/f4z/HCuzhHcuAkr/TojbPwHnd4LKw7f 20QiAdmN0rGaNjDj7L//f2RJ4k18pkP1Nhx/RxBgYTfSjhs2gz6BqEMaMp8N1SqNKLqb HXjIH7VdUkeNHNaKPGvpl/ihkq7MZ2xTjMlPFiFgbdQg3/vebNIpI2+8fc2MH/hhhYF0 a8BQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=mI/WBHaF62dkGQkIY6wgY3MU1lGRGBbq7f4d7H8A2VM=; b=iUx4TmiwiQ/HH4G7jWlA04XTGDcnNwR4tHyMFWQErESOn5OLHZxVRxpCZ0190LGdxO dyMr2tliHQX+5uyQwgGhwFHYzEVfMjjNj+CJeHWOVWbb7/47/cMxpsix4FyDE3bjszqn mlnsgA2LSUGRsoZI2RsQS2uulW/OE+D3DKeUS8e/vpJP1MTLx9TzaTs2yaHaf9poZjtT Lj9oE62LxgyvxfMSaVfrOkwHgGTfBwvVPNR7c06BlkJ1FkfcRWQYXZa8Jp/cXFFONWzK fP/liVr2yiJyHKTdqs/gVpB2XLEG3a3nwYs5+vyfgMQ2buEVLH+9f6S3RBBDHtef6mc5 SdfA== X-Gm-Message-State: AMCzsaWTUn0FalP+8kA8/8i1ceDf/yX/VwwsRwiFXANd8BWmNibmtWCy disyy5L4k/oIxbRKWeQcsDN8Rb5nxErXJDTKZF5/Sw== X-Google-Smtp-Source: ABhQp+REuow/qq6wRPuivqCiwy8iGnS1Y/BwQmXnhYzX7OPQIKhOJNHHULKBuFSm9u0X9UkdWwMCr/mpriU5nmvciOw= X-Received: by 10.223.132.163 with SMTP id 32mr592085wrg.218.1508160877273; Mon, 16 Oct 2017 06:34:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.197.78 with HTTP; Mon, 16 Oct 2017 06:34:36 -0700 (PDT) From: Purav Chovatia Date: Mon, 16 Oct 2017 19:04:36 +0530 Message-ID: Subject: 99% time spent in WAL wait events To: pgsql-performance@postgresql.org Content-Type: multipart/alternative; boundary="94eb2c0d0dde5aa78b055baa1136" List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org --94eb2c0d0dde5aa78b055baa1136 Content-Type: text/plain; charset="UTF-8" Hello, We are running workload on a EDB Postgres Advanced Server 9.6 and we see that 99% of the time is spent on WAL wait events: *System Wait Information WAIT NAME COUNT WAIT TIME % WAIT --------------------------------------------------------------------------- wal flush 564552 298.789464 41.67 wal write 521514 211.601124 29.51 wal file sync 521546 205.519643 28.66* Disk IO performance is not an issue and WAL is on a dedicated disk. Can somebody pls suggest if there is any possibility to improve this & how? We already tried wal_buffers=96m, wal_sync_method=open_sync/open_datasync, checkpoint_completion_target=0.9 but none of those helped. System has 32GB RAM and shared_buffers=8GB. All transactions are happening on a single table which has about 1.5m records and the table size is 1.7GB with just one PK index. Many Thanks Regards --94eb2c0d0dde5aa78b055baa1136 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

We are running workload on a EDB= Postgres Advanced Server 9.6 and we see that 99% of the time is spent on W= AL wait events:
System Wait Information

WAIT NAME COUNT WAIT TIME % WAIT
---------------------------------------------------------------------------=
wal flush 564552 298.789464 41.67
wal write 521514 211.601124 29.51
wal file sync 521546 205.519643 28.66

Disk IO performance is not an issue and WAL is on a dedicated disk.
Can somebody pls suggest if there is any possibility to improve this &= amp; how?

We already tried wal_buffers=3D96m, wal_sync_method=3Dop= en_sync/open_datasync, checkpoint_completion_target=3D0.9 but none of those= helped.

System has 32GB RAM and shared_buffers=3D8GB. All tran= sactions are happening on a single table which has about 1.5m records and the table size= is 1.7GB with just one PK index.


Many Thanks<= /div>

<= /span>
Regards
--94eb2c0d0dde5aa78b055baa1136--