crate
CrateDB is a distributed and scalable SQL database for storing and analyzing massive amounts of data in near real-time, even with complex queries. It is PostgreSQL-compatible, and based on Lucene.
Runssource: GitHubhomepageJavaApache-2.0commit 66927f3454e7
Java, Apache-2.0 licensed. The project labels itself: analytics, big data, cratedb, database, dbms, distributed, distributed database and distributed sql database.
crate runs. An Argusic agent installed it in 36 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
CrateDB 6.5.0-SNAPSHOT compiles from source, packages into a distribution tarball, launches as a single-node cluster on port 4200 (HTTP) and 5432 (PostgreSQL wire), answers SQL queries via HTTP API, and passes unit tests across all libs and server modules.
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.
- forbiddenapis: java.lang.ClassNotFoundException: java.util.SequencedCollection when scanning Lists.class1 minute
- Install time
- 36 minutes
- Cold machine to finish
- 37 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- curl -s http://127.0.0.1:4200/_sql -X POST -d '{"stmt":"SELECT version(), 1+1 AS result"}' returned 200 with rows containing version and result=2; mvnw test on 7 libs modules and server module all BUILD SUCCESS
- Model tokens used
- 178,468
- Exact commit tested
- 66927f3454e7
- 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.
Here's a summary of everything I observed and verified: **Install**: The project compiled and packaged successfully with `./mvnw compile` and `./mvnw packa… **Launch**: Extracted the distribution tarball; `bin/crate -v` printed "Version: 6.5.0-SNAPSHOT, Bu… **Tests**: Ran unit tests across `libs/shared`, `libs/dex`, `libs/cli`, `libs/guice`, `libs/sql-par… **Error**: The `forbiddenapis` check fails because `java.util.SequencedCollection` is referenced bu… tokens used 178,468 Here's a summary of everything I observed and verified: **Install**: The project compiled and packaged successfully with `./mvnw compile` and `./mvnw packa… **Launch**: Extracted the distribution tarball; `bin/crate -v` printed "Version: 6.5.0-SNAPSHOT, Bu… **Tests**: Ran unit tests across `libs/shared`, `libs/dex`, `libs/cli`, `libs/guice`, `libs/sql-par… **Error**: The `forbiddenapis` check fails because `java.util.SequencedCollection` is referenced bu…
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 Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 36 minutes to install, slower than the median of the 12 comparable projects Argusic has measured.
Of the 13 analytics projects Argusic has installed and timed, crate was the 13th fastest to reach a running state, and 10 of 13 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)
analyticsbig-datacratedbdatabasedbmsdistributeddistributed-databasedistributed-sql-databaseelasticsearchindustrial-iotiotiot-analyticsiot-databaseluceneolappostgresqlsqltime-seriestsdbvector-database
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/crate)Questions
- Does crate run?
- Yes. crate runs. Argusic installed and launched it on a clean machine in 36 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test crate?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 66927f3454e7. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test crate?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does crate take to install?
- 36 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 crate need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing crate?
- 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 crate compare with the alternatives?
- Of the 13 analytics projects Argusic has installed and timed, crate was the 13th fastest to reach a running state, and 10 of 13 reached one at all.
- Where is the evidence for crate?
- 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.