pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedwal_log_hints benchmarks
3+ messages / 2 participants
[nested] [flat]
* wal_log_hints benchmarks
@ 2019-06-14 13:46 Fabio Pardi <f.pardi@portavita.eu>
2019-06-17 02:01 ` Re: wal_log_hints benchmarks Michael Paquier <michael@paquier.xyz>
0 siblings, 1 reply; 3+ messages in thread
From: Fabio Pardi @ 2019-06-14 13:46 UTC (permalink / raw)
To: pgsql-performance@lists.postgresql.org
Hi,
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.
https://portavita.github.io/2019-06-14-blog_PostgreSQL_wal_log_hints_benchmarked/
comments are welcome.
regards,
fabio pardi
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: wal_log_hints benchmarks
2019-06-14 13:46 wal_log_hints benchmarks Fabio Pardi <f.pardi@portavita.eu>
@ 2019-06-17 02:01 ` Michael Paquier <michael@paquier.xyz>
2019-06-17 07:53 ` Re: wal_log_hints benchmarks Fabio Pardi <f.pardi@portavita.eu>
0 siblings, 1 reply; 3+ messages in thread
From: Michael Paquier @ 2019-06-17 02:01 UTC (permalink / raw)
To: Fabio Pardi <f.pardi@portavita.eu>; +Cc: pgsql-performance@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: wal_log_hints benchmarks
2019-06-14 13:46 wal_log_hints benchmarks Fabio Pardi <f.pardi@portavita.eu>
2019-06-17 02:01 ` Re: wal_log_hints benchmarks Michael Paquier <michael@paquier.xyz>
@ 2019-06-17 07:53 ` Fabio Pardi <f.pardi@portavita.eu>
0 siblings, 0 replies; 3+ messages in thread
From: Fabio Pardi @ 2019-06-17 07:53 UTC (permalink / raw)
To: Michael Paquier <michael@paquier.xyz>; +Cc: pgsql-performance@lists.postgresql.org
Hi Michael,
thanks for taking the time of reading it and for your feedback.
On 17/06/2019 04:01, Michael Paquier wrote:
>
> 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.
Having compression enabled on production on several dbs, I can tell you that WAL production goes down around 50% in my case.
In my post, compression brings down WAL files to 1/2 when wal_log_hints is not enabled, and 1/3 when it is.
So, about compressibility, I think that pgbench data behaves similarly to production data, orat least the prod data I have in my databases.
I am curious to know other people's experience in this ML.
>
> 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.
That's a good remark, thanks. I did not think about it and I will keep it in mind next time. I instead averaged the results over multiple runs, but setting an explicit number of transactions is the way to go.
Results, by the way, were quite stable over all the runs (in terms of generated WAL files and TPS).
regards,
fabio pardi
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2019-06-17 07:53 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2019-06-14 13:46 wal_log_hints benchmarks Fabio Pardi <f.pardi@portavita.eu>
2019-06-17 02:01 ` Michael Paquier <michael@paquier.xyz>
2019-06-17 07:53 ` Fabio Pardi <f.pardi@portavita.eu>
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