| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | pglz compression performance, take two |
| Date: | 2020-12-09 07:44:42 |
| Message-ID: | FEF3DC5E-4BC4-44E1-8DEB-DADC67046FE3@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi hackers!
A year ago Vladimir Leskov proposed patch to speed up pglz compression[0]. PFA the patch with some editorialisation by me.
I saw some reports of bottlenecking in pglz WAL compression [1].
Hopefully soon we will have compression codecs developed by compression specialists. The work is going on in nearby thread about custom compression methods.
Is it viable to work on pglz optimisation? It's about x1.4 faster. Or should we rely on future use of lz4\zstd and others?
Best regards, Andrey Borodin.
[0] https://www.postgresql.org/message-id/169163A8-C96F-4DBE-A062-7D1CECBE9E5D@yandex-team.ru
[1] https://smalldatum.blogspot.com/2020/12/tuning-for-insert-benchmark-postgres_4.html
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Reorganize-pglz-compression-code.patch | application/octet-stream | 21.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-12-09 07:55:04 | Re: Occasional tablespace.sql failures in check-world -jnn |
| Previous Message | Michael Paquier | 2020-12-09 06:37:50 | Re: get_constraint_index() and conindid |