olric
Distributed, in-memory key/value store and cache. It can be used as an embedded Go library and a language-independent service.
Runssource: GitHubGoApache-2.0commit c49c44a8816b
Go, Apache-2.0 licensed. The project labels itself: cache, database, distributed cache, distributed database, distributed hash table, distributed systems, in memory and in memory database.
olric runs. An Argusic agent installed it in 28 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Go 1.25.0 installed, project compiles, olric-server binary starts and handles RESP protocol commands (PING, DM.PUT/DM.GET/DM.DEL with TTL, PUB/SUB) on TCP port 3330, and 91+ unit/integration tests across 20+ packages 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 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.
- Go 1.25.0 pre-release had broken runtime (duplicate symbols in internal/abi and runtime)6 minutes
- Go compiler not installed4 minutes
- Install time
- 28 minutes
- Cold machine to finish
- 28 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- RESP protocol test via python against olric-server: PING -> +PONG, DM.PUT -> +OK, DM.GET -> value, DM.DEL -> :1, DM.GET missing -> -KEYNOTFOUND, SUBSCRIBE/PUBLISH -> message delivered, TTL expiry -> -KEYNOTFOUND after 3s. All sub-packages tests pass; root package tests pass except 2 pre-existing flaky tests (TestEmbeddedClient_Issue263 goroutine-leak check, TestDMap_LockWithTimeout_ErrLockNotAcquired_Cluster) that pass in isolation.
- Model tokens used
- 682,605
- Exact commit tested
- c49c44a8816b
- 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.
{'msg': 'Go 1.25.0 pre-release had broken runtime (duplicate symbols in internal/abi and ru…
],
'test_depth': 'tier1_real',
'verified_how': 'RESP protocol test via python against olric-server: PING -> +PONG, DM.PUT -> +…
'final_state': 'Go 1.25.0 installed, project compiles, olric-server binary starts and handles R…
}
print(json.dumps(r))
\"" in /work/repo
succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 28.0, "errors": [{"msg": "…
tokens used
682,605Replay 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 28 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.
- 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)
cachedatabasedistributed-cachedistributed-databasedistributed-hash-tabledistributed-systemsin-memoryin-memory-databasekey-valuekey-value-storenosqlredis
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/olric)Questions
- Does olric run?
- Yes. olric runs. Argusic installed and launched it on a clean machine in 28 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test olric?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c49c44a8816b. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test olric?
- The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does olric take to install?
- 28 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 olric need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing olric?
- 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.
- Where is the evidence for olric?
- 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.