riot

Go Open Source, Distributed, Simple and fastest efficient text/vector Search Engine

Runssource: GitHubGoApache-2.0commit 0219e1c26ca1

Go, Apache-2.0 licensed. The project labels itself: big data, go, golang, index, indexer, riot, search and search engine.

riot runs. An Argusic agent installed it in 18 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Go 1.26.10 toolchain installed under /tmp/go-toolchain, riot builds and its entire test suite passes with -race (984/984), CLI installs and runs, and the README index/query and CJK demos produce the documented 'match: example' and hit results.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.04 (measured)
recorded runs
2
last tested
stars
6,064
forks
469
open issues
0
watchers
1
size
14 MB
created
last push

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.

Time lost to each failure while testing riot, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • no Go toolchain in container (go: not found)3 minutes
  • go.mod requires go 1.26.0 so initially fetched go1.24.4 (superset not satisfied)2 minutes
  • I first ran 'riot snapshot <path> 1' on an index whose only snapshot is 2 and it printed a file-not-found error1 minute
Install time
18 minutes
Cold machine to finish
12 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
go test -race -count=1 -json ./... returned 984 pass / 0 fail; README write+read demo printed 'match: example'; /tmp/gobin/riot list returned 'snapshot: 2'
Model tokens used
96,502
Exact commit tested
0219e1c26ca1
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.

0
984
0
I have complete, verified numbers: 984 tests passed, 0 failed under `-race`. The errors encountered…
exec
/bin/sh -lc 'cd /work/repo && git status --short | head; echo "---"; ls /tmp/gobin /tmp/go-toolchai…
 succeeded in 0ms:
artifacts-in-tmp
All checks are complete and the repository is untouched. Final report:
tokens used
96,502
All checks are complete and the repository is untouched. 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.
  • 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 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 18 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.

Of the 12 go projects Argusic has installed and timed, riot was the 11th fastest to reach a running state, and 12 of 12 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.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.04
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

big-datagogolangindexindexerriotsearchsearch-enginevector-search

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/riot.svg)](https://argusic.com/subject/riot)

Questions

Does riot run?
Yes. riot runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test riot?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0219e1c26ca1. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test riot?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does riot take to install?
18 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 riot need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing riot?
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.
How does riot compare with the alternatives?
Of the 12 go projects Argusic has installed and timed, riot was the 11th fastest to reach a running state, and 12 of 12 reached one at all.
Where is the evidence for riot?
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.

Discussion