News for hackers. Stuff that matters.

A comment on Monitoring your own infrastructure using Grafana, InfluxDB, and CollectD. Parent comment

Re:Monitoring your own infrastructure using Grafana, InfluxD... by mekster on Tuesday July 21, 2020 @08:24PM (#23912512)
Can you refute the claim that TimescaleDB uses such a huge disk space that is 50 times larger than other time series database?

I see no reason to use it over VictoriaMetrics.

https://medium.com/@valyala/high-cardinality-tsdb-benchmarks...

[ Parent | on HN ]
Re:Monitoring your own infrastructure using Grafana, InfluxD... by PaulWaldman on Tuesday July 21, 2020 @08:38PM (#23912619)
Yes, I can refute that claim. TimescaleDB now provides built in compression.

https://docs.timescale.com/latest/using-timescaledb/compress...

[ Parent | on HN ]
Re:Monitoring your own infrastructure using Grafana, InfluxD... by mekster on Tuesday July 21, 2020 @08:47PM (#23912694)
You didn't refute it technically.

Are you saying the compression shrinks the data down to 2% on average?

If the compression only makes the data 10 times smaller (I think I'm being generous with that ratio), it's still 5 times larger than the others.

[ Parent | on HN ]
Re:Monitoring your own infrastructure using Grafana, InfluxD... by PaulWaldman on Tuesday July 21, 2020 @09:08PM (#23912861)
Completely anecdotal, but I went from 50B to 2B per point using the compression feature. Mind you this is for slow moving sensor data collected at regular 1 second intervals.

Prior to the compression feature, I had the same complaint. Timescale strongly advocated for using ZFS disk compression if compression was really required. Requiring ZFS disk compression wasn't feasible for me.

[ Parent | on HN ]