iotdb
Apache IoTDB
Runssource: GitHubhomepageJavaApache-2.0commit 25ab7941cebe
Java, Apache-2.0 licensed. The project labels itself: big data, database, iot, java, nosql, timeseries and tsdb.
iotdb runs. An Argusic agent installed it in 75 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Apache IoTDB 2.0.11-SNAPSHOT builds from source, passes focused unit tests, and runs as a standalone 1C1D cluster accepting SQL reads and writes over port 6667.
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.
- ConfigNode JVM dies silently ~30s after startup due to parent shell SIGHUP (exec ... & pattern in start script).12 minutes
- Gradle Enterprise extensions (in .mvn/) blocked build with connection timeouts to ge.apache.org.8 minutes
- No Java or Maven installed. Downloaded JDK 17 and Maven 3.9.6 manually.5 minutes
- Tsfile SNAPSHOT dependency (2.4.1-260806-SNAPSHOT) not in Maven Central. Added Apache snapshot repository to pom.xml so Maven can resolve it.3 minutes
- DataNode fails with InaccessibleObjectException: JDK 17 module system blocks cglib reflective access.3 minutes
- Install time
- 75 minutes
- Cold machine to finish
- 77 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- IoTDB 2.0.11-SNAPSHOT compiled successfully with mvn package -DskipTests -pl distribution -am. 12 unit tests passed (IoTDBDescriptorTest, AggregationDescriptorTest, AnalyzeUtilsTest, ExpressionAnalyzerTest). Standalone cluster (ConfigNode:10710 + DataNode:6667) started from distribution/ target. CLI connected and executed: 'CREATE DATABASE root.test' (ok), 'INSERT INTO root.test.wf01.wt01(timestamp, temperature) VALUES(1000, 25.5)' (ok), 'SELECT * FROM root.test.wf01.wt01' returned 1 row with value 25.5.
- Model tokens used
- 412,132
- Exact commit tested
- 25ab7941cebe
- 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.
<url>https://jitpack.io</url>
</repository>
<repository>
<id>apache.snapshots</id>
<url>https://repository.apache.org/content/repositories/snapshots/</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
Now let me compile the final report.
tokens used
412,132
Now let me compile the final report.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.
- Installed in 75 minutes.
- Recovered from all 5 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.
- Measured 2 times, so the result is not a one-off.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/iotdb)Questions
- Does iotdb run?
- Yes. iotdb runs. Argusic installed and launched it on a clean machine in 75 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test iotdb?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 25ab7941cebe. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test iotdb?
- The run that produced this verdict cost $0.37: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does iotdb take to install?
- 75 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 iotdb need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing iotdb?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for iotdb?
- 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.