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 37 minutes and hit 4 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 on JDK 17 using Maven wrapper, and runs as two JVMs (ConfigNode + DataNode) on a single machine, accepting CLI connections on port 6667, supporting tree-model SQL operations (CREATE DATABASE, INSERT, SELECT) against stored time-series data.
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.
- IoTDB servers require ~1.7GB heap by default, but container has only 754MB RAM. Servers crashed with OOM.15 minutes
- No JDK 17 installed in container. Required Java >= 17.1 minute
- No Maven installed. The mvnw wrapper downloaded Maven 3.9.12 automatically.
- mvn test-compile fails on 3 pre-existing errors in test files referencing BuiltinPipePlugin.OPC_UA_SINK symbol in OPC UA pipe tests.
- Install time
- 37 minutes
- Cold machine to finish
- 41 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- Built distribution with 'mvnw clean package -pl distribution -am -DskipTests' (BUILD SUCCESS). Started ConfigNode and DataNode with MEMORY_SIZE=384M/256M. Connected via CLI: 'echo "show databases" | sbin/start-cli.sh' returned login success. Executed CREATE DATABASE root.test (success), INSERT INTO root.test.wf01.wt01 (timestamp, temperature) values (now(), 22.5) (success), SELECT * FROM root.test.wf01.wt01 returned one row with temperature=22.5. Ran 67 unit tests (IoTDBDescriptorTest, PropertiesTest, DataNodeMemoryConfigTest, DirectoryStrategyTest, AuthorityCheckerTest, AuthorizerManagerTest, LoginLockManagerTest, UserTest, RoleTest, PathPrivilegeTest, DataBasePrivilegeTest, TablePrivilegeTest) all passed with 0 failures.
- Model tokens used
- 829,955
- 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.
echo "Actual install_minutes: The build took multiple attempts. Let me compute based on the observe… echo "First compile started around 10:30:10 UTC. Final server test at ~11:07 UTC." echo "Total: ~37 minutes." echo "" echo "Verified with: IoTDB CLI executed CREATE DATABASE, INSERT, SELECT queries successfully on run… succeeded in 0ms: Actual install_minutes: The build took multiple attempts. Let me compute based on the observed time… First compile started around 10:30:10 UTC. Final server test at ~11:07 UTC. Total: ~37 minutes. Verified with: IoTDB CLI executed CREATE DATABASE, INSERT, SELECT queries successfully on running s… tokens used 829,955
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 4 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 3 times, so the result is not a one-off.
What did not, or is not known
- Took 37 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
Of the 4 big-data projects Argusic has installed and timed, iotdb was the 4th 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)
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 37 minutes, hitting 4 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. 3 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.27: 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?
- 37 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?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does iotdb compare with the alternatives?
- Of the 4 big-data projects Argusic has installed and timed, iotdb was the 4th fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for iotdb?
- All 3 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.