4. Comparing HammerDB results

HammerDB implements a workload based on the TPC-C specification however does NOT implement a full specification TPC-C benchmark and the transaction results from HammerDB cannot be compared with the official published TPC-C benchmarks in any manner. Official Audited TPC-C benchmarks are extremely costly, time consuming and complex to establish and maintain. The HammerDB implementation based on the specification of the TPC-C benchmark is designed to capture the essence of TPC-C in a form that can be run at low cost on any system bringing professional, reliable and predictable load testing to all database environments. For this reason HammerDB results cannot and should NOT be compared or used with the term tpmC in any circumstance. You are permitted however to observe for your own benefit whether a correlation exists between the ratios of HammerDB results conducted on different systems and officially, audited and published results. HammerDB workloads produce 2 statistics to compare systems called TPM and NOPM respectively. TPM is the specific database transactional measurement typically defined as the number of user commits plus the number of user rollbacks. Being database specific TPM values cannot be compared between different database types. On the other hand the NOPM value is based on a metric captured from within the test schema itself. As such NOPM (New Orders per minute) is a performance metric independent of any particular database implementation and is the recommended primary metric to use.