HammerDB v6.0 extends HammerDB beyond interactive database benchmarking into automated build, benchmark, metrics capture and result sharing workflows. The release includes new CI and pipeline automation capabilities for MariaDB, MySQL and PostgreSQL, enhanced database and operating system metrics, Active Session History support for MySQL and MariaDB, improved performance profile comparison, extended percentile reporting and richer metadata capture for submitted benchmark results.
The release also includes packaging and runtime changes, including single-file executables for the HammerDB graphical interface, command line interface and web service. HammerDB remains fully open source under the GNU General Public License v3.0, and the move to single-file executable binary releases does not change the HammerDB license or the availability of the source code.
HammerDB v6.0 introduces CI and pipeline automation capabilities for repeatable database build and benchmark workflows. These capabilities are intended for users who want to automate the process of building a database from source, installing or preparing the database, creating a HammerDB schema, running a workload and collecting the resulting performance data.
The v6.0 release adds CI and pipeline capabilities for MariaDB, MySQL and PostgreSQL. This includes database-specific automation for pipeline execution, schema sizing, workload execution and result capture. The automation functionality also includes fixes to ensure that virtual user state is handled correctly across mixed automated, graphical and command line runs.
Automated workflows require more environment preparation than standard HammerDB use. In addition to the HammerDB package itself, the target system must have the compiler, database build dependencies, database client libraries, runtime libraries and operating system tools required by the selected database and workload. For this reason, the CI and pipeline features should be treated as an advanced capability rather than as a required installation step.
HammerDB v6.0 extends the Metrics functionality with additional database and system measurements. The release adds I/O metrics including IOPS and MB/s, improves messages when operating system metrics collection cannot start because required tools such as sysstat are not installed, and adds database metrics options for MySQL and MariaDB.
HammerDB v6.0 also adds an Active Session History metrics viewer for MySQL and MariaDB. This viewer is designed to help correlate benchmark activity with database activity during a workload run. It provides a database-focused view of active sessions so that users can better understand what the database is doing while HammerDB is driving load.
PostgreSQL metrics are also updated in v6.0, including PostgreSQL 18 Active Session History support and improvements to pgsentinel discovery. MariaDB TPROC-H adds support for engine independent statistics, and MariaDB/MySQL pre-created database builds can disable foreign key checks during loading where appropriate.
HammerDB v6.0 adds further support for sharing benchmark results and capturing the metadata needed to make those results easier to interpret. TPROC-H result sharing now includes database version and metrics information, and submitted results can include more detailed system, hardware and software fields.
HammerDB v6.0 supports uploading benchmark result artifacts for publication or review. This allows a locally generated HammerDB result to be shared as hosted benchmark evidence rather than remaining only as a local result file. Uploaded results can include the workload result, database version, metrics and system metadata needed to make the result easier to understand and compare.
The purpose of this additional metadata is to make benchmark results more useful as evidence. A result is easier to compare and reproduce when it includes information about the database version, system configuration, hardware, software, workload settings and metrics collected during the run.
HammerDB v6.0 also simplifies the artifact submit process. This improves the workflow for users who want to publish or archive benchmark evidence from a HammerDB run.
HammerDB v6.0 improves performance profile comparison and response time reporting. Timing profiles now support reservoir sampling and extended percentile reporting, making it easier to compare latency distributions as well as headline throughput.
These improvements are intended to make performance profiles more useful for repeatable testing, regression detection and evidence-based comparison of database configurations. HammerDB can show not only whether one run achieved a higher throughput, but also whether response time behaviour changed across the run.
HammerDB v6.0 enables the HammerDB web service to run as an SCGI application, improves web service jobs and pipelines HTML formatting, and fixes web form handling for proxy environments. These changes make the web service more suitable for deployment behind a web server or automation gateway.
The release also includes AWS cloud metadata detection fixes, automated schema sizing updates and improvements to pipeline result handling. These changes support the broader direction of HammerDB as a tool that can be used both interactively and as part of automated benchmark infrastructure.
HammerDB v6.0 New Features are all referenced to GitHub Pull Requests, where more details for each new feature and related pull requests can be found here:
[TPC-Council#897] Fix NULL Oracle Version reported for TPROC-H
[TPC-Council#894] Fix SQL Server GUI Scale Factor Option
[TPC-Council#893] Fix AWS cloud metadata detection
[TPC-Council#892] Fix virtual user state across mixed automated, GUI and CLI runs
[TPC-Council#891] Simplify artifact submit process
[TPC-Council#889] Update TPROC-C automated schema sizing
[TPC-Council#888] Add TPROC-H version and metrics to result sharing
[TPC-Council#885] Add database metrics options for MySQL and MariaDB
[TPC-Council#884] Fix Web Service Jobs and Pipelines HTML Formatting
[TPC-Council#880] Add I/O Metrics (IOPS/MB/s) to Metrics
[TPC-Council#879] Fix arithmetic in PostgreSQL stock update
[TPC-Council#878] Fix profile compare form and hide unsupported from automation
[TPC-Council#877] Fix form warnings for proxy
[TPC-Council#876] Add CI/Pipeline Automation for MySQL
[TPC-Council#875] Add PostgreSQL CI/Pipeline automation
[TPC-Council#870] Fix pgsentinel discovery for PostgreSQL metrics
[TPC-Council#868] Improve performance profile comparison, response time reporting, and CI bug fixes
[TPC-Council#867] Auto fix PostgreSQL choice of functions or stored procedures
[TPC-Council#866] Fix Windows clearline in default COLOR
[TPC-Council#865] Standardise Cluster Connect Pool terminology
[TPC-Council#864] Add reservoir sampling, extended percentile support to timing profiles and boxplots
[TPC-Council#863] Add Active Session History (ASH) metrics viewer for MySQL and MariaDB
[TPC-Council#861] Remove arbitrary upper limit on num_vu for schema build
[TPC-Council#860] Add CI/Pipeline capabilities for MariaDB
[TPC-Council#859] Add Detailed System, Hardware, and Software Fields to Results
[TPC-Council#856] Fix PostgreSQL vacuum running on wrong database
[TPC-Council#854] Update ASH metrics for PostgreSQL 18
[TPC-Council#835] Update TPROC-H GUI Options for all Scale Factors
[TPC-Council#830] Improve message if metstart fails because sysstat is not installed
[TPC-Council#829] Add engine independent statistics to MariaDB TPROC-H
[TPC-Council#825] Disable FK checks for MariaDB/MySQL pre-created database builds
[TPC-Council#818] Fix invalid command wapp-url
[TPC-Council#810] Update Tcl/Tk and TkPath versions
[TPC-Council#808] Enable Web Service to run as SCGI application
[TPC-Council#805] Update ticklecharts package
[TPC-Council#797] Add handling of innodb_snapshot_isolation to MariaDB
[TPC-Council#796] Add catch to CLI stty command on Linux
[TPC-Council#795] Fix permission denied on loading database libraries on Windows
[TPC-Council#794] Copyright message UTF-8
[TPC-Council#789] Docker Updates related to version 5.0
[TPC-Council#787] Fix steprun replica timing