xodus
Transactional schema-less embedded database used by JetBrains YouTrack and JetBrains Hub.
Runssource: GitHubJavaApache-2.0commit 18f573765aff
Java, Apache-2.0 licensed. The project labels itself: database, db, embedded database, entity store, java, key value, kotlin and log structured.
xodus runs. An Argusic agent installed it in 7 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
JetBrains Xodus builds cleanly with Gradle 8.5 + JDK 17, all 1386 tests pass across 9 modules (xodus-utils, xodus-openAPI, xodus-compress, xodus-crypto, xodus-environment, xodus-entity-store, xodus-query, xodus-lucene-directory-v2, xodus-environment-crash-tests), and the xodus-tools CLI jar runs and responds to commands.
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 JDK found in container (Java not installed)1 minute
- Install time
- 7 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- `./gradlew build` exited 0 with 'BUILD SUCCESSFUL', 1386 tests passed (0 failures, 0 errors, 12 skipped); `java -jar tools/build/libs/xodus-tools.jar Reflect` printed usage message confirming the CLI tool launches
- Model tokens used
- 70,881
- Exact commit tested
- 18f573765aff
- 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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.
-r validate Roots -t Traverse actual root -d<file name> Dump utilization to a file (can be used with the '-t' option) -c Copy and compact actual root to a new environment (environment path 2 is mandator… -cp Copy and compact actual root to a new environment with forced prefixing (environm… -u display stored Utilization -p print PersistentEntityStore tables usage (must be used with the '-t' option) -cl<file name> CLean particular file before any reflection The project is a pure-Java/Kotlin embedded database library (JetBrains Xodus). No running app serve… tokens used 70,881 The project is a pure-Java/Kotlin embedded database library (JetBrains Xodus). No running app serve…
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 7 minutes to install, slower than the median of the 13 comparable projects Argusic has measured.
Of the 14 database projects Argusic has installed and timed, xodus was the 12th fastest to reach a running state, and 13 of 14 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 7 minutes after the clone.
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)
databasedbembedded-databaseentity-storejavakey-valuekotlinlog-structurednosqlschema-lesssnapshot-isolationtransactionalxodusyoutrack
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/xodus)Questions
- Does xodus run?
- Yes. xodus runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test xodus?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 18f573765aff. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test xodus?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does xodus take to install?
- 7 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 xodus need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing xodus?
- 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 xodus compare with the alternatives?
- Of the 14 database projects Argusic has installed and timed, xodus was the 12th fastest to reach a running state, and 13 of 14 reached one at all.
- Where is the evidence for xodus?
- 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.