Compression is pretty OP actually. I have a table with zabbix where each chunk is around 3.6GB before and 200MB after compression. I really wonder about the performance of accessing data in those chunks though.
Hi! Compression is OP indeed! As for performance, this is an excerpt from the Timescale docs: "Because a single row takes up less disk space than many rows, it decreases the amount of disk space required, and can also speed up some queries." Pretty neat if you ask me!
Hey Devesh! Absolutely. A TimescaleDB compression policy applies to chunks, the partitions that make up a hypertable. When all of the data in a chunk is older than the set compression policy, it will be dropped, regardless of whether it's compressed or not. 🔥
Compression is pretty OP actually. I have a table with zabbix where each chunk is around 3.6GB before and 200MB after compression. I really wonder about the performance of accessing data in those chunks though.
Hi! Compression is OP indeed! As for performance, this is an excerpt from the Timescale docs: "Because a single row takes up less disk space than many rows, it decreases the amount of disk space required, and can also speed up some queries." Pretty neat if you ask me!
What happens if I need to modify a compressed value ?
How can I do that ?
Can we define retention policy on compressed data?
Hey Devesh! Absolutely. A TimescaleDB compression policy applies to chunks, the partitions that make up a hypertable. When all of the data in a chunk is older than the set compression policy, it will be dropped, regardless of whether it's compressed or not. 🔥