HammerDB v6.0 can create a result artifact from a completed benchmark report. The result artifact is a structured JSON file that contains the benchmark result, database version, workload configuration, system metadata, timing data and metrics where available. This JSON file is the artifact used when submitting a HammerDB result for publication or review. The PDF report is useful for local review and archiving, but the JSON result artifact is the submission file.
At the end of the Benchmark Report, review the disclaimer text and use the report links to save and share the result. Select Save HammerDB result artifact first to download the JSON result artifact, then select Share HammerDB result artifact to open the TPC/HammerDB submission workflow.
The browser downloads the HammerDB result artifact as a JSON file. Keep this file available because it will be uploaded or pasted into the submission page for validation.
Upload or drag the saved HammerDB JSON result artifact into the validation area.
When the artifact validates successfully, the submission page shows a result preview. Review the database, benchmark, result and system fields before continuing. Click Copy to JSON to add the artifact to the clipboard.
After validation, continue to GitHub. GitHub opens an editor for the result artifact in the results repository. Paste the artifact content and click commit changes.
Propose the change in GitHub. If you do not have direct write access, GitHub creates a new fork and starts a pull request. Review the commit message and select Propose changes.
After the pull request is reviewed and accepted, the submitted artifact can appear on the HammerDB result artifacts page. This page lists submitted artifacts and provides links to view the published result report.
The published report presents the submitted result as benchmark evidence, including the benchmark result, configuration, response time information and system metadata supplied in the artifact.
Charts generated from the submitted artifact can be used to review the result visually. Submitted HammerDB result artifacts are community-submitted benchmark evidence for review and publication. They are not official TPC benchmark results and do not replace the requirements of an official TPC benchmark disclosure.
