This PR has not had any activity in the past 30 days, so the needs-attention label has been added to it.
If you do not have enough time to follow up on this PR or you think it's no longer relevant, consider closing it.
The needs-attention label signals to maintainers that something has fallen through the cracks. No action is needed by you; your PR will be kept open and you do not have to respond to this comment. The label will be removed the next time this job runs if there is new activity.
Thank you for your contributions!

Hey, thanks for the PR! I don't doubt the compression is better, but there's no information in the package for what the comparison of CPU/memory consumption is.

I'd like to see some tests here:

• A benchmark comparing golang/snappy and klauspost/compress/snappy, with a custom stat for post-compression size.
• A fuzz test that ensures anything compressed using klauspost/compress/snappy can be decompressed with golang/snappy

It looks like both Prometheus and Loki have explored switching to klauspost/compress/snappy, but found that compression performs worse in those cases.

Those were done at the storage-level and not at the client-side, so that's not necessarily an indication that it'll perform worse in Alloy, but definitely an indication that we should add benchmarks and validate.