4mo ago

The power of interning: making a time series database 2000x smaller in Rust

gendignoux.com

The power of interning: making a time series database 2000x smaller in Rust | Blog | Guillaume Endignoux

Rust @programming.dev

cm0002 @lemmy.world

4mo ago

The power of interning: making a time series database 2000x smaller in Rust

gendignoux.com /blog/2025/03/03/rust-interning-2000x.html

10 comments

If you're storing your data as json on disk, you probably never cared about efficient storage anyway.
- They thought "data lake" was a physical description.
Rust was the important factor in this result. That's why it's in the headline. It wasn't the hugely inefficient way of storing the data initially. Not at all.
FFS, you could just have run gzip on it probably.
- FFS, you could just have run gzip on it probably.
  Gzip doesn't reduce your data's size by 2000x. Of course this could be done by other languages as well, but running gzip on your data doesn't keep it accessible.
  Even turning the data into a Parquet file would've been a massive improvement, while keeping it accessible, but it likely would not have been 2000x smaller. 10x, maybe.
  edit: zip: about 10x; 7zip about 166x (from ~10GB to 60MB) - still not 2000x
  
  It all depends on the data entropy. Formats like JSON compress very well anyway. If the data is also very repetitive too then 2000x is very possible.
Hmm I think just using SQLite or DuckDB with normalised data would probably get you 99% of the way there...
- It all depends on how it's represented on disk though and how the query is executed. Sqlite only supports numbers and strings, and if you keep using a VARCHAR, a read of those rows are going to have materialize a string into memory inside the sqlite library. DuckDB has more types, but if you're using varchars everywhere, something has to read that string into memory unless you can push down logic into a query that doesn't actually have to read the actual value, such as one that can use indices.
  The best way is to change the representation on disk, such as converting low-cardinality columns like the station into a numeric id. A standard int being four bytes is a lot more efficient than an n-byte string + a header and it can be compared by value.
  This is where file formats, like Parquet, shine. They're oriented more towards parsing by systems. JSON is geared towards human parsing.

10 comments