At TPCTC 2025 in London, we set out where HammerDB was heading next: not just repeatable database benchmarking, but making the evidence behind a benchmark easier to save, review and share.
HammerDB v6.0 is now live.
This release adds result artifacts that can be saved, reviewed and shared through the TPC-Council community results repository on GitHub.
A benchmark number on its own is not enough. The workload, system, configuration and metrics behind the result matter too.
HammerDB v6.0 provides a cleaner path from a test run to open, transparent database performance evidence.
New in HammerDB v6.0
The main new features in HammerDB v6.0 include:
- Result artifacts for saving, reviewing and sharing benchmark results.
- Automated benchmark pipelines for repeatable database performance testing.
- Profile comparisons to compare benchmark runs and identify what changed.
- ASH-style analysis for MySQL and MariaDB to show waits, contention and database activity during a workload.
- System discovery to capture platform details as part of the benchmark result.
- I/O metrics to record IOPS and throughput alongside the benchmark output.
- Response Time percentiles and sampling for enhanced l
Community result sharing
The result artifact is the first step in making HammerDB benchmark results easier for the community to share and review.
It captures the key information behind a run, including the workload, database, system, configuration, metrics and result data. This gives users more context than a single performance number and makes it easier to understand how a result was produced.
These are HammerDB community results. They are not audited TPC benchmark results, but they provide an open way for users to share benchmark evidence through the TPC-Council GitHub workflow.
Database support
HammerDB continues to support Oracle, SQL Server, Db2, PostgreSQL, MySQL and MariaDB.
HammerDB v6.0 supports TPROC-C for transactional workloads and TPROC-H for analytical workloads.
Follow-up posts
This is the first in a short series of posts on HammerDB v6.0.
Follow-up posts will look in more detail at result artifacts, automated benchmark pipelines, profile comparisons, ASH for MySQL and MariaDB, system discovery and I/O metrics.