Remove Benchmarking Remove Event Remove Hardware Remove Servers
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

Impact of Querying Table Information From information_schema

Percona

On MySQL and Percona Server for MySQL , there is a schema called information_schema (I_S) which provides information about database tables, views, indexes, and more. Disclaimer : This blog post is meant to show a less-known problem but is not meant to be a serious benchmark. Results for Percona Server for MySQL 5.7

Cache 107
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

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

HammerDB

This enables the user to compare and contrast performance across different benchmark scenarios. include/server -I/opt/postgresql-14.1/include/internal The example has a configuration set to illustrate a number of wait events and has therefore not been configured for performance. Metrics view for benchmark. pgsentinel.c /opt/postgresql-4.1/pgsentinel/src$

Metrics 62
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. I had attended these events when I was based in the UK, but became one of the organizers.

Tuning 52
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

Seer: leveraging big data to navigate the complexity of performance debugging in cloud microservices

The Morning Paper

Last time around we looked at the DeathStarBench suite of microservices-based benchmark applications and learned that microservices systems can be especially latency sensitive, and that hotspots can propagate through a microservices architecture in interesting ways. When available, it can use hardware level performance counters.

article thumbnail

10 tips for migrating from monolith to microservices

Dynatrace

Because monolithic applications combine database, client-side interfaces, and server-side application elements in a single executable, they’re difficult to understand, even for their own administrators. Unsurprisingly, organizations are breaking away from monolithic architectures and moving toward event-driven microservices.