VICTORIAMETRICS OBSERVABILITY BLOG · SEP 9, 2022

Grafana Mimir and VictoriaMetrics: performance tests

Benchmarking VictoriaMetrics and Grafana Mimir on the same hardware — rebuilt with the live charts sitting where the published figures belong.

We compare the performance and resource usage of VictoriaMetrics and Grafana Mimir clusters running under the same workload and on the same hardware.

The tables below are copied from the post; the charts are live Graphy v2 rebuilds. The two views answer different questions: what was published then, and what the reader can inspect now.

VictoriaMetrics and Mimir — total CPU used

Traced/estimated from the published Grafana figure.

Rebuilt in Graphy v2 · original VictoriaMetrics post ↗

Disk space used — Mimir vs VictoriaMetrics

Traced/estimated from the published Grafana figure.

Rebuilt in Graphy v2 · original VictoriaMetrics post ↗

Grafana Mimir — resource allocation by component

Exact values from the article table.

Rebuilt in Graphy v2 · original VictoriaMetrics post ↗

VictoriaMetrics cluster — resource allocation by component

Exact values from the article table.

Rebuilt in Graphy v2 · original VictoriaMetrics post ↗

What the original post published

The Mimir table lists 43.2 CPU units and 283 GiB of memory across the sampled components. The VictoriaMetrics table lists 44 CPU units and 208 GiB of memory. The live rebuild keeps those figures attached to the component labels, so a reader can hover the comparison rather than decode a raster export.