pinot
Apache Pinot: a real-time analytics database for low-latency SQL and vector search, serving user-facing and agent-facing applications
Runssource: GitHubJavaApache-2.0commit 0a53497fddfc
Java, Apache-2.0 licensed. The project labels itself: ai agents, analytics, database, distributed database, java, kafka, olap and real time analytics.
pinot runs. An Argusic agent installed it in 26 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Apache Pinot 1.7.0-SNAPSHOT builds from source with JDK 25, produces a binary distribution tarball (998 MB), passes 3803 unit tests across pinot-common and pinot-spi, and the pinot-admin CLI tool starts and lists all subcommands.
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. 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.
- Install time
- 26 minutes
- Cold machine to finish
- 26 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- ./mvnw -pl pinot-common -am test returned 'Tests run: 2912, Failures: 0, Errors: 0, Skipped: 6'; ./mvnw -pl pinot-spi -am test returned 'Tests run: 891, Failures: 0, Errors: 0, Skipped: 0'; ./mvnw clean install -DskipTests -Pbin-dist -Pbuild-shaded-jar returned 'BUILD SUCCESS' (1563 goals); ./bin/pinot-admin.sh --help from the distribution listed all 33 subcommands; ./mvnw -pl pinot-segment-local -am -Dtest=GzipCompressorTest -Dsurefire.failIfNoSpecifiedTests=false test returned BUILD SUCCESS
- Model tokens used
- 207,285
- Exact commit tested
- 0a53497fddfc
- 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 attempt that decided the verdict above. 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.
exec /bin/sh -lc "# First mvn command output shows \"Finished at: 2026-11-06T10:02:59Z\" # Current time is 2026-11-06T10:25ish # That's about 22 minutes since first build command started (was issued slightly before 10:02:59) # Total elapsed: approximately 26 minutes echo \"Install and test completed in approximately 26 minutes\"" in /work/repo succeeded in 0ms: Install and test completed in approximately 26 minutes Here is the summary: tokens used 207,285 Here is the summary:
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.
- Nothing broke on the way: zero errors between clone and running.
- 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
- Took 26 minutes to install, slower than the median of the 114 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 115 ai-agents projects Argusic has installed and timed, pinot was the 101st fastest to reach a running state, and 85 of 115 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.
- Following its own README: the documented path worked with nothing to fix.
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)
ai-agentsanalyticsdatabasedistributed-databasejavakafkaolapreal-time-analyticssqlvector-databasevector-search
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/pinot)Questions
- Does pinot run?
- Yes. pinot runs. Argusic installed and launched it on a clean machine in 26 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test pinot?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0a53497fddfc. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test pinot?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does pinot take to install?
- 26 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 pinot need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing pinot?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does pinot compare with the alternatives?
- Of the 115 ai-agents projects Argusic has installed and timed, pinot was the 101st fastest to reach a running state, and 85 of 115 reached one at all.
- Where is the evidence for pinot?
- 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.