Fabian Groffen
Fabian Groffen
is the max close to what you expect?
hmmm, sorry to bother you with this obvious fail ...
Hmmm. The retrieval code for carbon-c-relay ensures a unique list of servers is returned. See https://github.com/grobian/carbon-c-relay/blob/master/consistent-hash.c#L418. In your scenario you use use multiple caches on a single host, which carbon-c-relay...
I use LZ4_compress_fast_continue to write to the compressed stream, e.g. it's (re-)using dictionaries etc. from previously compressed blocks to gain better compression ratio. The function belongs to the "Streaming Compression...
_safe_ here is because the input data is random, a crash may not happen due to misformed data. Yesterday I tried to produce a simple example using lz4 util, but...
I just tested, using two relays, it works as expected. The problem appears to be that nothing seems to be able to just generate block streams, except the c-library itself.
I'm thinking I better introduce a "heavy-weight" lz4 mode if you want to send lz4 data from a non-C producer.
since the read you refer to is appending to the buffer, a short read will not harm, decompression will fail, the next read will complete the block though
Any reason why you need LZ4 here? Would zstd for instance be ok for you too?
Alright. I've just looked into creating the "heavy-weight" lz4 support, but (at least on the writer side) it isn't that simple. It most likely won't compress much because it will...