pikiwidb
Pikiwidb is a Redis-Compatible database developed by Qihoo's infrastructure team.
Runssource: GitHubC++BSD-3-Clausecommit 54693ce5882f
C++, BSD-3-Clause licensed. The project labels itself: nosql, nosql data storage, nosql databases, pikiwidb, redis, redis interfaces and rocksdb.
pikiwidb runs. An Argusic agent installed it in 27 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
PikiwiDB 4.0.2 builds from source, starts on port 9221, correctly answers Redis PING/SET/GET/INFO commands, and all unit tests in pstd, net, and storage 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.
- cmake detected 192 CPU cores from /proc/cpuinfo causing OOM kills24 minutes
- autoconf not found on system, no root to install packages3 minutes
- Install time
- 27 minutes
- Cold machine to finish
- 46 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- python3 sent Redis PING/SET/GET/INFO via raw TCP to 127.0.0.1:9221 returned +PONG/+OK/$5hello/$1564INFO; 18 unit test binaries for pstd, net, and storage all PASSED
- Model tokens used
- 293,622
- Exact commit tested
- 54693ce5882f
- 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.
**final_state**: PikiwiDB 4.0.2 builds from source, starts on port 9221, correctly answers Redis PI…
tokens used
293,622
Here is my summary of the full mission.
**Errors encountered:**
1. **autoconf not installed** — no root access to `apt install`, so I built GNU M4 1.4.19 and Autoc…
2. **OOM during parallel builds** — `cmake_host_system_information` and `/proc/cpuinfo` reported 19…
**install_succeeded**: true — build completed successfully, producing `/work/repo/output/pika` (121…
**launch_succeeded**: true — pika 4.0.2 starts, listens on port 9221, and responds to Redis protoco…
**verified_how**: `python3 -c 'import socket; s=socket.socket(); s.connect(("127.0.0.1",9221)); s.s…
**test_depth**: tier1_real
**final_state**: PikiwiDB 4.0.2 builds from source, starts on port 9221, correctly answers Redis PI…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 27 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 BSD-3-Clause, as reported by its host.
- Measured 2 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)
nosqlnosql-data-storagenosql-databasespikiwidbredisredis-interfacesrocksdb
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/pikiwidb)Questions
- Does pikiwidb run?
- Yes. pikiwidb runs. Argusic installed and launched it on a clean machine in 27 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test pikiwidb?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 54693ce5882f. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test pikiwidb?
- The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does pikiwidb take to install?
- 27 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 pikiwidb need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing pikiwidb?
- 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 pikiwidb?
- 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.