Re: Compressed TOAST Slicing - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: Compressed TOAST Slicing
Date
Msg-id 58B7237A-CBEC-47CF-AC5B-EFA52D6093BB@yandex-team.ru
Whole thread Raw
In response to Re: Compressed TOAST Slicing  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

> 9 апр. 2019 г., в 22:30, Tom Lane <tgl@sss.pgh.pa.us> написал(а):
>
> The proposal is kind of cute, but I'll bet it's a net loss for
> small copy lengths --- likely we'd want some cutoff below which
> we do it with the dumb byte-at-a-time loop.

Ture.
I've made simple extension to compare decompression time on pgbench-generated WAL [0]

Use of smart memcpy unless match length is smaller than 16 (sane random value) gives about 20% speedup to decompression
time.
Sole use of memcpy gives smaller effect.

We will dig into this further.

Best regards, Andrey Borodin.


[0] https://github.com/x4m/test_pglz


pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: pg_dump is broken for partition tablespaces
Next
From: Tom Lane
Date:
Subject: Re: Commit message / hash in commitfest page.