do we need a different strategy for compressible payloads?

[brayniac]

Currently, we take a naive approach of a payload (either a value for cache or a message for pubsub) having a fixed number of random bytes to achieve a target compression ratio. These bytes are grouped at the head of the payload (ignoring the additional header we pack into pubsub messages to track timing and integrity).

We should do some analysis to determine if the entropy needs to be spread throughout the payload, either by shuffling the bytes, or using a reduced set of symbols, or ...

It would be interesting to know if this even effects the compression/decompression overheads in an appreciable way for expected value/message sizes.

[brayniac]

This is not needed after #301 which shuffles the bytes around.