compress VS sqlite-zstd

There's a pure-go zstd at https://github.com/klauspost/compress - it's likely faster than running the upstream zstd under Wazero.

It's no surprise that "fast" Go libraries are actually just assembly: https://github.com/klauspost/compress/blob/master/zstd/seqdec_amd64.s (just one file out of several, for just one architecture, for just one compression algorithm!)

There is a reasonably feature complete implementation of Zstd for Go: https://github.com/klauspost/compress/tree/master/zstd

It may not offer the same API 1:1, but it has no interoperability issues that I've encountered. So, I just think no one has bothered to implement it in Rust because most use cases don't mind the added bloat you're talking about. Plus, other comments I've seen suggest that you can actually tune the size of the zstd library, although I'm not sure if the Rust bindings expose that.

Thanks again for your review/comment!!! Btw, are you the author of this repo https://github.com/klauspost/compress because I love it!!!

I noticed Github returns "This page is taking too long to load" with status code 502 for https://github.com/klauspost/compress but rest of their urls works fine. Anyone know why would that be the case ?

Cloning the repo works perfectly well.

git clone https://github.com/klauspost/compress

Recent versions of zstd definitely don't obsolete LZ4, or else I don't think the author would still be contributing to both...

And if you're going to play with Snappy, you might find S2, which was linked on HN relatively recently, interesting. [1]

[1] - https://github.com/klauspost/compress/tree/master/s2

Compression method appears to be zstandard and uses https://github.com/klauspost/compress, for those wondering like I was.

OMG u/klauspost is this you? https://github.com/klauspost/compress/tree/master/s2

Have you compared LZ4 to other compression algorithms, zstd for example? ( https://github.com/phiresky/sqlite-zstd )

Given that LiteFS operates at the filesystem layer via FUSE, have you considered it against designs that use built-in features native to some filesystems? For example, I've considered a similar system design based on a single ZFS primary node that streams ZFS snapshots to reader nodes. With some coordination service (e.g. consul) it could still allow for the whole node promotion process.

There's library to compress sqlite databases with extensions like sqlite-zstd.

You can also try sqlite-zstd [1], which is an sqlite extension allows transparent compression of individual rows by automatically training dictionaries based on groups of data rows.

Disclaimer: I made it and it's not production ready

[1] https://github.com/phiresky/sqlite-zstd