HammerDB Result Submission Instructions
How a user runs a benchmark from the GUI, CLI, or Web Service and submits the resulting HammerDB artifact for review and publication.

Entry points
  • GUI: run the benchmark and view the generated job in the Web Service Jobs page.
  • CLI: run the benchmark from HammerDB CLI, then open the saved job in the Web Service Jobs page.
  • Web Service: trigger the pipeline from the Web Service and wait for the benchmark job to complete.
Submission sequence
  1. Open the completed job from the HammerDB Jobs Web Service page.
  2. Review the benchmark report and confirm the result details.
  3. Click Share with TPC-OSS and download the JSON artifact.
  4. A reviewer can render the supplied JSON artifact from a review URL at any point before publication.
  5. Upload the JSON artifact to GitHub and create a pull request.
  6. Validation checks run, the reviewer inspects the result, and the pull request is merged when accepted.
  7. The accepted artifact appears on the leaderboard and the public result report is available.

Reviewer note: The review page is deliberately URL-based. It allows the workload and result artifact to be checked before the JSON is published on the leaderboard.
1. View completed benchmark job in HammerDB Web Service
After running a benchmark from the GUI, CLI, or Web Service pipeline, open the HammerDB Jobs page in the Web Service. The completed Benchmark Run appears under TPROC-C or TPROC-H. Select the Jobid link for the benchmark result you want to submit.
Completed benchmark job in HammerDB Web Service Jobs page
2. Open the job artifact index
The job page exposes the report, output, benchmark settings, database details, result, status, transaction count, system information, metrics, timestamp, and response times. Open Benchmark report to view the human-readable result.
Job artifact index with report and result links
3. Review the benchmark report
The benchmark report is the user-facing evidence page. It summarizes the database, release, benchmark, HammerDB version, timestamp, primary metric, benchmark configuration, response times, and system information.
HammerDB benchmark report summary
4. Use Share with TPC-OSS from the report
At the end of the report, the disclaimer explains that this is a HammerDB result artifact and not an official audited TPC result. Use Share with TPC-OSS to start the submission workflow.
Share with TPC-OSS control on the benchmark report
5. Submit HammerDB result artifact page
The submit page previews the result and gives the user a two-step process: download the JSON artifact, then upload that same file to GitHub. The page also shows the correct upload folder path for the result.
Submit HammerDB result artifact page
6. Reviewer preview page from a JSON URL at any point
This is the review page, not the upload page. A reviewer can open a review URL at any point to render the supplied JSON artifact before it is published on the leaderboard. This lets the reviewer inspect the workload, result, configuration, response times, system information, and charts directly from the artifact.
Reviewer preview page rendered from a JSON URL
7. Downloaded JSON artifact
The JSON artifact is downloaded locally. This file is the machine-readable result that is uploaded to GitHub for review. The filename is the HammerDB Jobid with a .json extension.
Downloaded HammerDB JSON artifact file
8. Upload the JSON artifact to GitHub
On GitHub, upload the JSON artifact into the folder shown by the submit page. Use Create a new branch for this commit and start a pull request so the result can be reviewed before publication.
Uploading the JSON artifact to GitHub
9. Open the pull request
GitHub opens a pull request from the user branch into master. The pull request title and description should identify the submitted result and any relevant user comments.
GitHub pull request for the submitted result
10. Pull request checks and review
The pull request records who submitted the result, shows the uploaded JSON file, and runs validation checks. The reviewer can use the review URL to inspect the workload before merging.
Pull request checks and review
11. Merged pull request
After review and successful checks, the pull request is merged. Merging the pull request publishes the accepted JSON artifact into the result repository.
Merged pull request publishing the artifact
12. Leaderboard updated
The public HammerDB Result Artifacts page reads the accepted JSON artifacts and updates the leaderboard. The submitted result now appears with the database, release, primary metric, configuration, system summary, timestamp, and a View report button.
HammerDB Result Artifacts leaderboard with new result
13. Published result report
The published result report is rendered from the accepted artifact. It provides the final public view of the result, including benchmark configuration, response times, system information, and charts.
Published HammerDB result report
Reviewer notes
The reviewer can inspect the workload from the JSON review URL at any point. This is separate from the GitHub upload page and separate from the final published leaderboard report.
  • Check the primary metric and benchmark identity.
  • Check benchmark configuration and system data.
  • Check response times, metrics, and charts.
  • Confirm the artifact validates and is suitable for publication.
  • Merge the pull request only after review is complete.