One of the latest benchmarks we made was ‘VictoriaMetrics: scaling to 100 million metrics per second’. While the fact of such scale for VictoriaMetrics is noteworthy on its own, the benchmark tool used to generate that load is usually overlooked. In this blog post I’ll explain in more details the challenge of running such benchmarks.
In monitoring, the term cardinality defines the number of unique time series stored in TSDB. The higher is cardinality, the more resources are usually required for metrics processing and querying. Let’s see how Cardinality explorer can help us here.
Benchmarking VictoriaMetrics and Grafana Mimir on the same hardware
When looking for a most scalable open source time series database, what are the criteria to care about? Read this blog to get our recommendations.
VictoriaMetrics has new production ready builds for ARM