tantivy
Tantivy is a full-text search engine library inspired by Apache Lucene and written in Rust
Runssource: GitHubRustMITcommit 6182c6062f4d
Rust, MIT licensed. The project labels itself: rust and search engine.
tantivy runs. An Argusic agent installed it in 10 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Tantivy 0.27.0 builds with cargo on stable Rust 1.99.1, all 1970 workspace tests pass, and the basic_search example indexes documents and returns correct search hits end to end.
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.
- No Rust toolchain (rustc/cargo) present in container3 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- cargo test --workspace exited 0 with 1970 passed / 0 failed / 10 ignored; ./target/debug/examples/basic_search exited 0 and printed the JSON hit {"title":["The Old Man and the Sea"]} plus a BM25 score of 17.563686
- Model tokens used
- 71,337
- Exact commit tested
- 6182c6062f4d
- 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.
All verification is complete. Summary of what I observed: - Installed Rust 1.99.1 via rustup (user-local, no root needed) since no toolchain shipped in the c… - `cargo build --workspace` finished cleanly (`Finished dev profile ... in 1m 05s`). - `cargo test --workspace` exited 0: **1970 passed, 0 failed, 10 ignored** across the tantivy works… - `./target/debug/examples/basic_search` exited 0: it indexed 3 in-memory docs, ran a query, and pr… tokens used 71,337 All verification is complete. Summary of what I observed: - Installed Rust 1.99.1 via rustup (user-local, no root needed) since no toolchain shipped in the c… - `cargo build --workspace` finished cleanly (`Finished dev profile ... in 1m 05s`). - `cargo test --workspace` exited 0: **1970 passed, 0 failed, 10 ignored** across the tantivy works… - `./target/debug/examples/basic_search` exited 0: it indexed 3 in-memory docs, ran a query, and pr…
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 1 error 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.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 10 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
Of the 6 rust projects Argusic has installed and timed, tantivy was the 6th fastest to reach a running state, and 5 of 6 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 10 minutes after the clone.
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/tantivy)Questions
- Does tantivy run?
- Yes. tantivy runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test tantivy?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6182c6062f4d. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test tantivy?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tantivy take to install?
- 10 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 tantivy need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tantivy?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does tantivy compare with the alternatives?
- Of the 6 rust projects Argusic has installed and timed, tantivy was the 6th fastest to reach a running state, and 5 of 6 reached one at all.
- Where is the evidence for tantivy?
- 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.