3 ms·
https://github.com/VictoriaMetrics/VictoriaMetrics#cardinality-limiter https://github.com/VictoriaMetrics/VictoriaMetrics#cardinali... If I understand this cor
by dikei 3y ago
https://github.com/VictoriaMetrics/VictoriaMetrics#cardinality-limiter https://github.com/VictoriaMetrics/VictoriaMetrics#cardinali...
If I understand this correctly, it deals with high cardinality by dropping data. The operators need to monitor for this and adjust their data to lower the cardinality.
- narism 3y agoFrom your link: > By default VictoriaMetrics doesn't limit the number of stored time series. They have put out some benchmarks showing VictoriaMetrics ingesting 40M time series: https://valyala.medium.com/high-cardinality-tsdb-benchmarks-victoriametrics-vs-timescaledb-vs-influxdb-13e6ee64dd6b https://valyala.medium.com/high-cardinality-tsdb-benchmarks-...
- eclark 3y agoThis is the only longer term scalable solution. High cardinality for TSDB's have to be dealt with by dropping. Or you run out of storage, write rate, memory, or network. It's possible to smooth this loss out (by assuming a normal distribution of lost data) if it's noticed and limited. Though I do not think there's any commercial TSDB that does that automatically.