3 ms·
Click house is a great DB but still not the best at storing timeseries metrics. Do you have plans to incorporate a db optimized for time series storage?
by gregwebs 4y ago
Click house is a great DB but still not the best at storing timeseries metrics. Do you have plans to incorporate a db optimized for time series storage?
- datalopers 4y agoI see this viewpoint occasionally but have never seen what features a TSDB offers that Clickhouse can’t do just as effectively if not better?
- hiyer 4y agoI would have thought better compression was one, but it looks like Clickhouse now supports all the time series-optimized encodings like delta and gorilla - https://altinity.com/blog/2019/7/new-encodings-to-improve-clickhouse https://altinity.com/blog/2019/7/new-encodings-to-improve-cl....
- RhodesianHunter 4y agoClickhouse is absolutely incredible at storing time series metrics.
- ankitnayan 4y agoWhat does your schema for metrics look like? Using materialised views? I am particularly interested in storing metrics with labels(key/val pairs) Eg, Prometheus metrics. You can't flatten them out into columns due to high dimensionality(can need millions of columns). Do you store the labels in an array?
- datalopers 4y agoNot the person you're replying to, but you can see how SigNoz did it here [1] Essentially you add: keys Array(String), values Array(String) and write the pairs accordingly. https://github.com/SigNoz/signoz/blob/develop/deploy/docker-swarm/clickhouse-setup/docker-entrypoint-initdb.d/init-db.sql https://github.com/SigNoz/signoz/blob/develop/deploy/docker-...