toydb
Distributed SQL database in Rust, written as an educational project
Runssource: GitHubRustApache-2.0commit 0f42c9fc3b5c
Rust, Apache-2.0 licensed. The project labels itself: database, distributed, mvcc, raft, rust and sql.
toydb runs. An Argusic agent installed it in 4 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
toyDB server starts as single-node leader, listens on 127.0.0.1:9601/9701, and the toysql client successfully creates tables, inserts rows, and querys them
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.
- Rust not installed
- localhost resoles to IPv6 causing bind error 99
- Install time
- 4 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- cargo test --release exited 0, 291 unit + 5 integration tests passed; toydb --version printed 'toydb 1.0.0'; toysql client executed CREATE TABLE, INSERT, SELECT * returning 3 rows correctly
- Model tokens used
- 230,359
- Exact commit tested
- 0f42c9fc3b5c
- 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.
**Tests**: `cargo test --release` — 291 unit tests and 5 integration tests all passed, 0 failures. **Launch**: `toydb --version` → `toydb 1.0.0`. Server starts, elects itself leader, listens on SQL:… **End-to-end verification**: Created a table, inserted 3 rows, and retrieved them via `SELECT *` — … **Error encountered**: `localhost` resolves to IPv6 in this container causing `Cannot assign reques… tokens used 230,359 Everything is verified and working. Here's the summary: **Install**: Rust toolchain was missing from the container. Installed via rustup (stable + required… **Tests**: `cargo test --release` — 291 unit tests and 5 integration tests all passed, 0 failures. **Launch**: `toydb --version` → `toydb 1.0.0`. Server starts, elects itself leader, listens on SQL:… **End-to-end verification**: Created a table, inserted 3 rows, and retrieved them via `SELECT *` — … **Error encountered**: `localhost` resolves to IPv6 in this container causing `Cannot assign reques…
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 4 minutes.
- Recovered from all 2 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 Apache-2.0, 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 30 database projects Argusic has installed and timed, toydb was the 15th fastest to reach a running state, and 24 of 30 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 4 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/toydb)Questions
- Does toydb run?
- Yes. toydb runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test toydb?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0f42c9fc3b5c. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test toydb?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does toydb take to install?
- 4 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 toydb need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing toydb?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does toydb compare with the alternatives?
- Of the 30 database projects Argusic has installed and timed, toydb was the 15th fastest to reach a running state, and 24 of 30 reached one at all.
- Where is the evidence for toydb?
- 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.