From: Michael Paquier <michael@paquier.xyz>
To: Fabio Pardi <f.pardi@portavita.eu>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: wal_log_hints benchmarks
Date: Mon, 17 Jun 2019 11:01:07 +0900
Message-ID: <20190617020107.GF3153@paquier.xyz> (raw)
In-Reply-To: <43552731-a0ba-e9f5-838a-e1553d8ee705@portavita.eu>
References: <43552731-a0ba-e9f5-838a-e1553d8ee705@portavita.eu>
On Fri, Jun 14, 2019 at 03:46:30PM +0200, Fabio Pardi wrote:
> Maybe of some interest for the past, present and future community, I
> benchmarked the impact of wal_log_hints with and without wal_compression
> enabled.
pgbench data is rather compressible per the format of its attributes,
hence I am ready to bet that the compressibility would much much less
if you use random text data for example.
The amount of WAL generated also depends on the time it takes to run a
transactions, and on the checkpoint timing, so I think that would you
get better results by using a fixed number of transactions if you use
pgbench, but that won't compare as much as a given workload in one
session so as you can make sure that the same amount of WAL and full
pages get generated.
--
Michael
Attachments:
[application/pgp-signature] signature.asc (832B, ../20190617020107.GF3153@paquier.xyz/2-signature.asc)
download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: michael@paquier.xyz, f.pardi@portavita.eu, pgsql-performance@lists.postgresql.org
Subject: Re: wal_log_hints benchmarks
In-Reply-To: <20190617020107.GF3153@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox