tiny-lsm
A KV storage engine based on LSM Tree, supporting Redis RESP
Runssource: GitHubhomepageC++MITcommit 838b53b6e989
C++, MIT licensed. The project labels itself: cpp, database, key value store, lsm tree, nosql and redis.
tiny-lsm runs. An Argusic agent installed it in 2 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 13 test binaries (106 tests) pass, the example binary runs correctly printing key-value operations, and the Redis-protocol TCP server starts and responds to RESP PING with +PONG.
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- pybind11 requires Python dev headers not installed2 minutes
- gmock package not available in xmake-repo1 minute
- unzip binary not available in container1 minute
- xmake local-repo 'build' directory didn't exist1 minute
- Install time
- 2 minutes
- Cold machine to finish
- 15 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- xmake run test_skiplist (12 passed), test_config (1), test_utils (9), test_block (10), test_blockmeta (6), test_block_cache (4), test_memtable (11), test_sst (8), test_lsm (12), test_compact (5), test_redis (11), test_wal (6), test_wisckey (11): all 106 tests passed. Server started and responded to RESP PING with +PONG on port 6379.
- Model tokens used
- 198,072
- Exact commit tested
- 838b53b6e989
- 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 attempt that decided the verdict above. 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.
2026-10-24T10:31:10.491435Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce… All tests pass and the server responds to Redis PING. Let me compute the final result exec /bin/sh -lc 'date +%s' in /work/repo succeeded in 0ms: 1792837877 All 106 tests pass and the server works. Here's the final report: 2026-10-24T10:31:27.283295Z ERROR codex_core::session: failed to record rollout items: thread 01a16… 2026-10-24T10:31:27.283376Z ERROR codex_core::session: failed to record rollout items: thread 01a16… tokens used 198,072 All 106 tests pass and the server works. Here's the final report:
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 2 minutes, faster than the median of the 3 comparable projects Argusic has measured.
- Recovered from all 4 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 MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 cpp projects Argusic has installed and timed, tiny-lsm was the 1st fastest to reach a running state, and 3 of 4 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.
- A quick evaluation: it was running 2 minutes after the clone.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tiny-lsm)Questions
- Does tiny-lsm run?
- Yes. tiny-lsm runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test tiny-lsm?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 838b53b6e989. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test tiny-lsm?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tiny-lsm take to install?
- 2 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 tiny-lsm need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tiny-lsm?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does tiny-lsm compare with the alternatives?
- Of the 4 cpp projects Argusic has installed and timed, tiny-lsm was the 1st fastest to reach a running state, and 3 of 4 reached one at all.
- Where is the evidence for tiny-lsm?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.