The downside is that (a) Sprintz requires the data to be quantised to fixed point integers, usually fine if the data is coming out of a sensor of some sort and (b) the Huffman coding step of Sprintz requires dynamic memory allocation, whilst Gorilla is almost trivially implemented without it.
Also see Chimp, which proposes some small tweaks to Gorilla to improve its performance: https://dl.acm.org/doi/abs/10.14778/3551793.3551852
https://duckdb.org/docs/current/guides/sql_features/asof_joi...
Are there workloads time series databases can do where DuckDB would be a bad fit?
but it can do delta and bitpacking which is also kinda neat