article thumbnail

Why you should benchmark your database using stored procedures

HammerDB

HammerDB uses stored procedures to achieve maximum throughput when benchmarking your database. HammerDB has always used stored procedures as a design decision because the original benchmark was implemented as close as possible to the example workload in the TPC-C specification that uses stored procedures. On MySQL, we saw a 1.5X

article thumbnail

How to Assess MySQL Performance

HammerDB

Regardless of whether the computing platform to be evaluated is on-prem, containerized, virtualized, or in the cloud, it is crucial to consider several essential factors. There are several ways to find out this information with the easiest way being by referring to the documentation. For storage, FIO is generally used. 4.22 %usr 38.40

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

The Importance of Selecting the Proper Azure VM Size

SQL Performance

Migrating an on-premises SQL Server instance to an Azure Virtual Machine (VM) is a common method to migrate to Azure. Microsoft has helped simplify things by creating multiple types of virtual machines. High performance compute – Fastest and most powerful CPU virtual machines. Benchmark Test. VM Types and Sizes.

Azure 76
article thumbnail

HammerDB CLI 101

HammerDB

If the library failed to load consult the HammerDB documentation on installing and configuring your libraries with the PATH environment variable for Windows or LIBRARY_PATH environment for Linux. This will show the benchmark options dialog. Benchmark Options. and benchmark set with the bm argument. librarycheck.

article thumbnail

HammerDB v4.3 New Features Pt1: Graphical Metrics for PostgreSQL

HammerDB

This enables the user to compare and contrast performance across different benchmark scenarios. The example shows a TPROC-C workload running with 4 Active Virtual Users. Metrics view for benchmark. When a benchmark workload has completed, use the selection tool in the graph to select the metrics for a period of time of interest.

Metrics 62
article thumbnail

HammerDB v4.0 New Features Pt1: TPROC-C & TPROC-H

HammerDB

First of all it has always been clear in the HammerDB documentation that the TPROC-C/TPC-C and TPROC-H/TPC-H workloads have not been ‘real’ audited and published TPC results instead providing a tool to run workloads based on these specifications. This was both expensive and time consuming to configure.

C++ 40
article thumbnail

HammerDB v4.6 New Features Pt1: Python CLI Interface

HammerDB

If you need a different version of Python you can build HammerDB from source as detailed in the documentation to use any version of Python 3 that you wish. Vuser 1:1 Active Virtual Users configured Vuser 1:TEST RESULT : System achieved 39945 NOPM from 92893 SQL Server TPM Vuser 1:Gathering timing data from Active Virtual Users.