I released version v0.9.0, that is substantially more performant on large entries, like in @seb5law 's use-case.
Compression is now disabled, as it adds more drawbacks than benefits (large entries experience much slower writes, and small entries do not benefit much from compression anyway). This release is still completely backward compatible.
I will consider re-adding compression as a feature in a later release, but only after careful benchmarking, and with a way for the user to configure its parameters.
I will also add benchmarks with Benchee before version 1.0.0, to avoid these kinds of easily detectable performance regressions.
