VictoriaMetrics
VictoriaMetrics: fast, cost-effective monitoring solution and time series database
Runssource: GitHubhomepageGoApache-2.0commit 018bc7808882
Go, Apache-2.0 licensed. The project labels itself: database, grafana, graphite, influxdb, kubernetes, metrics, monitoring and observability.
VictoriaMetrics runs. An Argusic agent installed it in 13 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
VictoriaMetrics single binary builds, runs as an HTTP server on port 8428 returning valid responses, and the full unit test suite (131 packages) plus integration tests pass cleanly.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- 13 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- make victoria-metrics built binary; binary --version printed version; server started on :8428 and curl GET / returned 200 OK with HTML page; make test ran 131 unit test packages all ok; go test apptest/tests -skip cluster/legacy ran integration tests and all passed
- Model tokens used
- 113,845
- Exact commit tested
- 018bc7808882
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 1…
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 13, "errors": [], "test_de…
exec
/bin/sh -lc "cat <<'JSONEOF'
{\"install_succeeded\":true,\"launch_succeeded\":true,\"install_minutes\":13,\"errors\":[],\"test_d…
JSONEOF" in /work/repo
succeeded in 0ms:
{"install_succeeded":true,"launch_succeeded":true,"install_minutes":13,"errors":[],"test_depth":"ti…
tokens used
113,845Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 13 minutes to install, slower than the median of the 35 comparable projects Argusic has measured.
Of the 36 database projects Argusic has installed and timed, VictoriaMetrics was the 32nd fastest to reach a running state, and 29 of 36 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- Following its own README: the documented path worked with nothing to fix.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
databasegrafanagraphiteinfluxdbkubernetesmetricsmonitoringobservabilityopentelemetryopentsdbotlpprometheuspromqlthanostsdb
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/victoriametrics)Questions
- Does VictoriaMetrics run?
- Yes. VictoriaMetrics runs. Argusic installed and launched it on a clean machine in 13 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test VictoriaMetrics?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 018bc7808882. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test VictoriaMetrics?
- The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does VictoriaMetrics take to install?
- 13 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does VictoriaMetrics need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing VictoriaMetrics?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does VictoriaMetrics compare with the alternatives?
- Of the 36 database projects Argusic has installed and timed, VictoriaMetrics was the 32nd fastest to reach a running state, and 29 of 36 reached one at all.
- Where is the evidence for VictoriaMetrics?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.