quickwit
Cloud-native OSS search engine for observability
Runssource: GitHubhomepageRustApache-2.0commit af0591a36e16
Rust, Apache-2.0 licensed. The project labels itself: big data, cloud native, cloud storage, distributed tracing, log management, logs, open source and rust.
quickwit runs. An Argusic agent installed it in 15 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Quickwit 0.9.1 builds from source, runs as a server on localhost:7280, serves REST API, health check, index creation, JSON document ingestion, and full-text search all verified working.
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.
- cargo-nextest not installed4 minutes
- Rust toolchain not installed1 minute
- protoc not installed1 minute
- pre-existing test failure: test_concatenate_multiple_field returns values in wrong order
- Docker not available; integration tests requiring Docker services (S3, Kafka, Postgres) skipped
- make fmt requires nightly toolchain
- Install time
- 15 minutes
- Cold machine to finish
- 36 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- cargo nextest run across 15+ crates: 1080+ tests passed (1 known pre-existing failure skipped). Server launched on 127.0.0.1:7280, /health/livez returned true, created index test-index via POST /api/v1/indexes (HTTP 200), ingested JSON docs via POST /api/v1/test-index/ingest, searched with query body:* returning 1 hit, query body:log returning 1 hit
- Model tokens used
- 534,849
- Exact commit tested
- af0591a36e16
- 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.
**Errors encountered:**
1. **No Rust toolchain** — Rust was missing. Fix: installed via `rustup` (stable 1.98.1).
2. **No protoc** — Protocol Buffers compiler was missing. Fix: downloaded prebuilt `protoc` 27.0 fr…
3. **No cargo-nextest** — Required by the test runner. Fix: `cargo install cargo-nextest` (compiled…
4. **Pre-existing test failure** — `test_concatenate_multiple_field` in `quickwit-doc-mapper` asser…
5. **No Docker** — Docker is not available in this container. The `make test-all` flow and integrat…
6. **`make fmt` requires nightly** — Not installed, but stable rustfmt reports no errors (only warn…
exec
/bin/sh -lc "echo \"ARGUSIC_RESULT:{\\\"install_succeeded\\\":true,\\\"launch_succeeded\\\":true,\\…
succeeded in 0ms:
tokens used
534,849Replay 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 15 minutes, faster than the median of the 3 comparable projects Argusic has measured.
- Recovered from all 6 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 4 big-data projects Argusic has installed and timed, quickwit was the 2nd fastest to reach a running state, and 4 of 4 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
Topics (from GitHub)
big-datacloud-nativecloud-storagedistributed-tracinglog-managementlogsopen-sourcerustsearch-enginetantivy
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/quickwit)Questions
- Does quickwit run?
- Yes. quickwit runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test quickwit?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit af0591a36e16. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test quickwit?
- The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does quickwit take to install?
- 15 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 quickwit need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing quickwit?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does quickwit compare with the alternatives?
- Of the 4 big-data projects Argusic has installed and timed, quickwit was the 2nd fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for quickwit?
- 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.