25 MB lightweight cross-platform database client for 100+ databases, including MySQL, PostgreSQL, SQLite, Redis, MongoDB, DuckDB, SQL Server, and Dameng. Built-in AI, MCP Server, CLI, desktop and Docker. | 轻量级跨平台数据库管理工具,支持 MySQL、PostgreSQL、SQLite、Redis、MongoDB、达梦等 100+ 数据库,提供桌面端、Docker、CLI、内置 AI 助手和 MCP。
IoTDB JDBC vs Go driver benchmark
This standalone benchmark preserves the JDBC-versus-Go comparison used before
the production IoTDB Agent migrated to Go. It compares the released Apache
IoTDB 2.0.8 JDBC and Go clients against the same Tree-model server and
fixture, measuring cold process plus connection startup and warm query latency
while fully decoding every returned cell.
The default fixture contains 10,000 rows in root.dbx_bench.d1. Workloads are:
SHOW DATABASES- one timestamp point query
- a 100-row range query
- a full scan of all fixture rows
Start IoTDB
For example, run the matching standalone Docker image:
docker run --rm --name dbx-iotdb-bench -p 6667:6667 apache/iotdb:2.0.8-standalone
Wait until port 6667 is ready before starting the benchmark.
Run
From the repository root:
python3 agents/drivers/iotdb/bench/run.py \
> /tmp/dbx-iotdb-driver-benchmark.json
The runner builds both candidates from this benchmark directory, recreates the fixture, alternates cold-start and connected-RSS samples, then runs three warm workload rounds with alternating candidate order. It does not build or modify the production IoTDB Agent.
Configuration
IOTDB_HOST,IOTDB_PORT,IOTDB_USERNAME,IOTDB_PASSWORDBENCH_ROWS, default10000BENCH_FETCH_SIZE, default1024BENCH_STARTUPS, default5BENCH_RSS_SAMPLES, default3BENCH_ROUNDS, default3BENCH_ORDER, defaultjdbc,go; usego,jdbcto check order effectsBENCH_WARMUPS, default3BENCH_METADATA_ITERATIONS, default20BENCH_POINT_ITERATIONS, default100BENCH_RANGE_ITERATIONS, default30BENCH_SCAN_ITERATIONS, default5BENCH_PREPARE=falseto preserve an existing fixtureBENCH_SKIP_BUILD=trueto reuse existing benchmark artifacts
Run both candidates against the same server and do not change the fixture or fetch size between candidates. This is a client-side comparison, not an IoTDB server throughput benchmark.