From: | Rahila Syed <rahilasyed90(at)gmail(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, Rahila Syed <rahilasyed(dot)90(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Fwd: [REVIEW] Re: Compression of full-page-writes |
Date: | 2014-08-18 11:19:48 |
Message-ID: | CAH2L28s6Etv8nT7kUgOFxH71mU0xAB+YR=Yk1NrnF18_ohT_RA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>According to the measurement result, the amount of WAL generated in
>"Multiple Blocks in one run" than that in "Single Block in one run".
>So ISTM that compression of multiple blocks at one run can improve
>the compression ratio. Am I missing something?
Sorry for using unclear terminology. WAL generated here means WAL that gets
generated in each run without compression.
So, the value WAL generated in the above measurement is uncompressed WAL
generated to be specific.
uncompressed WAL = compressed WAL + Bytes saved.
Here, the measurements are done for a constant amount of time rather than
fixed number of transactions. Hence amount of WAL generated does not
correspond to compression ratios of each algo. Hence have calculated bytes
saved in order to get accurate idea of the amount of compression in each
scenario and for various algorithms.
Compression ratio i.e Uncompressed WAL/compressed WAL in each of the above
scenarios are as follows:
Compression algo Multiple Blocks in one run Single Block in one run
LZ4 1.21 1.27
Snappy 1.19 1.25
pglz 1.14 1.16
This shows compression ratios of both the scenarios Multiple blocks and
single block are nearly same for this benchmark.
Thank you,
Rahila Syed
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2014-08-18 11:30:40 | Re: wrapping in extended mode doesn't work well with default pager |
Previous Message | furuyao | 2014-08-18 10:55:36 | Re: pg_receivexlog --status-interval add fsync feedback |