メニュー
Generic logic for DBClient benchmark test mode: DatabaseTester.bench() implementation conventions, concurrency model, and result calculation. Use this skill when modifying the performance-test framework or troubleshooting throughput/concurrency issues.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | dbclient-testmode-benchmark |
| description | Generic logic for DBClient benchmark test mode: DatabaseTester.bench() implementation conventions, concurrency model, and result calculation. Use this skill when modifying the performance-test framework or troubleshooting throughput/concurrency issues. |
TestExecutor.executeTest()
tester.connect()
tester.bench(connection, query, iterations, concurrency)
String bench(DatabaseConnection connection, String query, int iterations, int concurrency);
Most bench() methods use:
ExecutorService managing concurrency threads.CountDownLatch to wait for all threads ready/done.iterations / concurrency times execute(connection, query).| File | Responsibility |
|---|---|
src/main/java/com/apecloud/dbtester/commons/DatabaseTester.java | bench() interface |
src/main/java/com/apecloud/dbtester/commons/TestExecutor.java | Dispatches to bench() |
src/main/java/com/apecloud/dbtester/tester/MySQLTester.java | Reference JDBC benchmark implementation |
src/main/java/com/apecloud/dbtester/tester/RedisTester.java | Reference non-JDBC benchmark implementation |
iterations defaults to 1000concurrency defaults to 10java -jar build/libs/oneclient-1.0-all.jar \
-h 127.0.0.1 -P 3306 -u root -p password -d test \
-e mysql -t benchmark -q "SELECT 1" -i 10000 -m 50
| Symptom | Investigation Point |
|---|---|
| Throughput much lower than expected | Does each thread create a new connection? Is the connection reused? |
| High latency jitter | Missing warm-up, GC pauses, thread pool warm-up |
| Threads never finish | ExecutorService.awaitTermination() timeout settings |
| Unstable results | Whether iterations is divisible by concurrency; counting logic correctness |
bench() return-value format affects benchmark output of all engines; update their skill examples.Practical guide for adding a new database or middleware engine to DBClient. Use this skill when you need to introduce a new dbType.
Cross-cutting core mechanisms of DBClient: CLI argument parsing, DBConfig, TesterFactory, TestExecutor, and the DatabaseTester interface. Use this skill when modifying generic flows or adding engine registration, validation, or dependencies.
KV / coordination engines in DBClient: Redis, RedisCluster, Redis Sentinel, Camellia-Proxy, Etcd, and Zookeeper. Use this skill when adding, debugging, or modifying such a Tester.
Message-queue engines in DBClient: Kafka, Pulsar, RabbitMQ, and RocketMQ. Use this skill when adding, debugging, or modifying such a Tester.
Relational / JDBC-protocol-compatible engines in DBClient. Covers MySQL-compatible, PostgreSQL-compatible, Oracle, SQLServer, domestic / regulated databases, and analytical databases such as StarRocks, Doris, and ClickHouse. Use this skill when adding, debugging, or modifying such a Tester.
Search / log-retrieval engines in DBClient: Elasticsearch 8.x and OpenSearch. Use this skill when adding, debugging, or modifying such a Tester.