Ready
Select a HammerDB result artifact to begin.
1
Select your result artifact
Use the JSON downloaded from HammerDB. The benchmark data and configuration are preserved.
Drop your JSON artifact here
or choose a file from your computer
Result location:
2
Who is submitting this result?
Attribution is shown on the leaderboard and links directly to the submitter's GitHub profile.
Must match the GitHub account opening the pull request. The PR validation checks this identity.
An HTTPS image URL; displayed next to your company name.
This appears on the leaderboard and in the full result artifact.
3
Describe the TPROC-C workload
CPU-intensive and I/O-intensive are different test configurations. Make the distinction explicit.
Taken from the HammerDB workload configuration if recorded; otherwise state how the run was configured.
Database transaction-log and commit behaviour, not inferred from storage telemetry.
Required (20 characters minimum) for a CPU- or I/O-intensive badge. Can be based on a manual run; no pipeline required.
Older results lacking UAW and durability data remain unclassified. IOPS / MB/s by themselves do not prove a bottleneck.
4
Review and submit through GitHub
Your artifact will contain the benchmark evidence plus your additional submission information.
On GitHub paste the copied JSON into the new file, commit, and open a pull request. The contributor's GitHub login is checked against the value you entered.
These are community-submitted, unaudited results. A workload badge describes declared configuration, not a measured finding of CPU or storage saturation.
Inspect the generated JSON
Select an artifact to preview.

