4 ms·

its exciting that things are happening again in db-land. A few years ago it was Fractal Trees, then leveldb arrived and got wider adoption, then Facebook put i

its exciting that things are happening again in db-land. A few years ago it was Fractal Trees, then leveldb arrived and got wider adoption, then Facebook put it in MySQL with MyRocks etc. Very recently timescaledb did some really really interesting stuff with compressing tables, and I’m wondering if that is useable with non-time-series data too etc? I’m a heavy tokudb user because of the compression and I’m looking forward to seeing if a b+ lsm with compression is going to turn up in MySQL or even better Postgres.

continuations 7y ago
What made you pick TokuDB instead of MyRocks? I got the impression that TokuDB is pretty much dead. Hasn't Percona stopped updating TokuDB and is focusing on MyRocks instead?
- willvarfar 7y ago
  I picked tokudb before myrocks existed. Tokudb runs rings around myrocks. Particularly, it has better read/write perf and much better compression. But it will disappear by MySQL 9. Tokudb died because it wasn’t widely adopted nor sponsored, not because it was worse tech. I think the recent timescaledb stuff about compression is really promising. I hope Postgres moves towards built-in compression rather than telling people the fs should do it.
  - valyala 7y ago
    I hope TimescaleDB compression level will eventually reach VictoriaMetrics compression level for typical time series data :) [1] [1] https://medium.com/@valyala/measuring-vertical-scalability-for-time-series-databases-in-google-cloud-92550d78d8ae https://medium.com/@valyala/measuring-vertical-scalability-f...
StreamBright 7y ago
Is there any reason Postgres or other projects could not adopt tokudb's solution?
- willvarfar 7y ago
  Architecturally, MySQL went with a “the storage engine is a plug-in” and Postgres went with a more traditional “the storage is part of the core”. Postgres has slowly grown some ... tolerance ... for alternative storage engines, via federation and forks like greenplum and timescaledb that put their own engines in, but they are always feeling like second class citizens and hitting integration limits.

continuations 7y ago

What made you pick TokuDB instead of MyRocks? I got the impression that TokuDB is pretty much dead. Hasn't Percona stopped updating TokuDB and is focusing on MyRocks instead?

willvarfar 7y ago
I picked tokudb before myrocks existed. Tokudb runs rings around myrocks. Particularly, it has better read/write perf and much better compression. But it will disappear by MySQL 9. Tokudb died because it wasn’t widely adopted nor sponsored, not because it was worse tech. I think the recent timescaledb stuff about compression is really promising. I hope Postgres moves towards built-in compression rather than telling people the fs should do it.
- valyala 7y ago
  I hope TimescaleDB compression level will eventually reach VictoriaMetrics compression level for typical time series data :) [1] [1] https://medium.com/@valyala/measuring-vertical-scalability-for-time-series-databases-in-google-cloud-92550d78d8ae https://medium.com/@valyala/measuring-vertical-scalability-f...

StreamBright 7y ago

Is there any reason Postgres or other projects could not adopt tokudb's solution?

willvarfar 7y ago
Architecturally, MySQL went with a “the storage engine is a plug-in” and Postgres went with a more traditional “the storage is part of the core”. Postgres has slowly grown some ... tolerance ... for alternative storage engines, via federation and forks like greenplum and timescaledb that put their own engines in, but they are always feeling like second class citizens and hitting integration limits.