Remove Benchmarking Remove Latency Remove Testing Remove Virtualization
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

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

HammerDB

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. For TPC-C this meant enough available spindles to reduce I/O latency and for TPC-H enough bandwidth for data throughput.

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

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

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

Kubernetes for Big Data Workloads

Abhishek Tiwari

Containerized data workloads running on Kubernetes offer several advantages over traditional virtual machine/bare metal based data workloads including but not limited to. The workloads for both test environments ran on apples-to-apples configurations. better cluster resource utilization. portability between cloud and on-premises.

article thumbnail

PostgreSQL Connection Pooling: Part 4 – PgBouncer vs. Pgpool-II

Scalegrid

PgBouncer provides a virtual database that reports various useful statistics. Performance Testing. So, we pitted the two connection poolers head-to-head, using the standard pgbench tool, to see which one provides better transactions per second throughput through a benchmark test. Testing Conditions. Administration.

article thumbnail

The Speed of Time

Brendan Gregg

A Cassandra database cluster had switched to Ubuntu and noticed write latency increased by over 30%. CLI tools The Cassandra systems were EC2 virtual machine (Xen) instances. Note that Ubuntu also has a frame to show entry into vDSO (virtual dynamic shared object). This will slow this test a little.)

Speed 126