valkey
A flexible distributed key-value database that is optimized for caching and other realtime workloads.
Runssource: GitHubhomepageCBSD-3-Clausecommit 85d02f638880
C, BSD-3-Clause licensed. The project labels itself: cache, database, key value, key value store, nosql, redis, valkey and valkey client.
valkey runs. An Argusic agent installed it in 42 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Valkey builds from source, serves PING/SET/GET correctly, and both the full unit test suite (784 tests) and the integration test suite pass.
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 96.7 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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- googletest not found for unit tests5 minutes
- tcl not installed (no root)3 minutes
- unit test -Werror=float-equal breaks gmock headers2 minutes
- Install time
- 42 minutes
- Cold machine to finish
- 51 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- make -C src test-unit exited 0, all 784 unit tests passed; ./runtest --single unit/auth exited 0, 16 integration tests passed; valkey-server --version returned 'Valkey server v=255.255.255'; valkey-cli PING returned PONG, SET/GET roundtrip worked
- Model tokens used
- 457,690
- Exact commit tested
- 85d02f638880
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
[778/784] HashtableTest.scan (1743 ms) [779/784] QuicklistTest.quicklistVerifySpecificCompressionOfInteriorNodes (1089 ms) [780/784] QuicklistTest.quicklistRotate500Val5000TimesAtCompress (1205 ms) [781/784] HashtableTest.bucket_chain_length (2006 ms) [782/784] HashtableTest.iterator (2278 ms) [783/784] QuicklistTest.quicklistComprassionPlainNode (3527 ms) [784/784] HashtableTest.incremental_find (4436 ms) Directory /home/runner/.cache does not existAll UNIT TESTS PASSED! make[1]: Leaving directory '/work/repo/src/unit' make: Leaving directory '/work/repo/src' tokens used 457,690
Replay 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.
- Installed in 42 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed BSD-3-Clause, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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)
cachedatabasekey-valuekey-value-storenosqlredisvalkeyvalkey-client
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/valkey)Questions
- Does valkey run?
- Yes. valkey runs. Argusic installed and launched it on a clean machine in 42 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test valkey?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 85d02f638880. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test valkey?
- The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does valkey take to install?
- 42 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 valkey need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing valkey?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for valkey?
- All 3 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.