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. Benchmarking the target Two of the more popular database benchmarks for MySQL are HammerDB and sysbench. 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.

article thumbnail

CheriABI: enforcing valid pointer provenance and minimizing pointer privilege in the POSIX C run-time environment

The Morning Paper

Last week we saw the benefits of rethinking memory and pointer models at the hardware level when it came to object storage and compression ( Zippads ). The protections are hardware implemented and cannot be forged in software. At hardware reset the boot code is granted maximally permissive architectural capabilities.

C++ 61
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

A full understanding of why this is important requires some knowledge of the evolution of database hardware and software. The HammerDB TPROC-C workload by design intended as CPU and memory intensive workload derived from TPC-C – so that we get to benchmark at maximum CPU performance at a much smaller database footprint.

C++ 40
article thumbnail

Why OpenStack is like a Crowdfunded Viking Movie

VoltDB

It was – like the hypothetical movie I describe above – more than a little bit odd, as you could leave a session discussing ever more abstract layers of virtualization and walk into one where they emphasized the critical importance of pinning a network interface to a specific VM for optimal performance.

article thumbnail

What Adrian Did Next?—?Part 2?—?Sun Microsystems

Adrian Cockcroft

I became the Sun UK local specialist in performance and hardware, and as Sun transitioned from a desktop workstation company to sell high end multiprocessor servers I was helping customers find and fix scalability problems. We had specializations in hardware, operating systems, databases, graphics, etc.

Tuning 52