4 ms·
Postgres with timescaledb extension (community) along with zfs compression works flawless for me. Different approach than Myrocks, but worth a try!
by rrickardt 7y ago
Postgres with timescaledb extension (community) along with zfs compression works flawless for me. Different approach than Myrocks, but worth a try!
- willvarfar 7y agoHave you tried using the timescaledb compression instead of zfs? And how does this compare to uncompressed and to native Postgres tables? I think that if timescaledb can support time-based or mru-based compression and even row-store partitions then it would take things to the next level.
- mfreed 7y agoYou've probably seen this, but reposting: https://blog.timescale.com/blog/building-columnar-compression-in-a-row-oriented-database/ https://blog.timescale.com/blog/building-columnar-compressio... Our own experience was that most users were getting 3-6x compression running TimescaleDB with zfs. With our native compression -- which does columnar projections, where a type-specific compression algorithm is applied per column -- we see median compression rates across our users of 15x, while 25% of our users see more than 50x compression rates.