Re: pglz compression performance, take two

From: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pglz compression performance, take two
Date: 2021-06-28 16:33:53
Message-ID: B1D3105C-D68B-445F-B3DF-E3F41FE79C46@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Jun 28, 2021, at 9:05 AM, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> wrote:
>
> Is it worth sharting a static inline function that uses your optimization in other places?

s/sharting/sharing/

> How confident are you that your optimization really helps?

By which I mean, is the optimization worth the extra branch checking if (len >= 16)? Is the 14% speedup you report dependent on this extra complexity?

—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2021-06-28 16:41:47 Re: Deparsing rewritten query
Previous Message Mark Dilger 2021-06-28 16:05:04 Re: pglz compression performance, take two