> Upthread [0], Andres suggested dispatching to a different implementation for
> compile-time-known small lengths. Have you looked into that? In your
> original post, you noted a 14% regression for records smaller than 256 bytes,
> which is not an uncommon case for Postgres. IMO we should try to mitigate
> that as much as possible.
So, without adding even more conditional tests (causing more latency), I can expose a new macro called
COMP_CRC32C_SMALLthat can be called from known locations where the size is known to be 20bytes or less (or any fixed
sizeless than 256). Other than that, there is no method I know of to pre-decide calling a function based on input size.
Is there any concrete thought on this?
Paul
