Remove c
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.

article thumbnail

Grafana Dashboards: A PoC Implementing the PostgreSQL Extension pg_stat_monitor

Percona

This PoC demonstrates how to install and configure pg_stat_monitor in order to extract useful and actionable metrics from a PostgreSQL database and display them on a Grafana dashboard. Installation (example: CENTOS8, pg14) The simplest way to get pg_stat_monitor is to install it via Percona Distribution for PostgreSQL.

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

Introducing the PostgreSQL performance metrics viewer. HammerDB included a graphical performance metrics view for the Oracle database only. HammerDB includes the same functionality for PostgreSQL enabling the user to drill down on database metrics in real time. PostgreSQL Graphical Metrics. usr/bin/install -c -m 644./pg_stat_statements--1.4.sql./pg_stat_statements--1.8--1.9.sql./pg_stat_statements--1.7--1.8.sql./pg_stat_statements--1.6--1.7.sql./pg_stat_stateme

Metrics 62
article thumbnail

Why you need to know your site's performance poverty line (and how to find it)

Speed Curve

"I made my pages faster, but my business and user engagement metrics didn't change. The performance poverty line is the plateau at which changes to your website’s rendering metrics (such as Start Render and Largest Contentful Paint) cease to matter because you’ve bottomed out in terms of business and user engagement metrics.

article thumbnail

HammerDB for Managers

HammerDB

HammerDB is a software application for database benchmarking. Databases are highly sophisticated software, and to design and run a fair benchmark workload is a complex undertaking. The Transaction Processing Performance Council (TPC) was founded to bring standards to database benchmarking, and the history of the TPC can be found here.

article thumbnail

How to maximize CPU performance for PostgreSQL 12.0 benchmarks on Linux

HammerDB

HammerDB doesn’t publish competitive database benchmarks, instead we always encourage people to be better informed by running their own. So over at Phoronix some database benchmarks were published showing PostgreSQL 12 Performance With AMD EPYC 7742 vs. Intel Xeon Platinum 8280 Benchmarks . bin/createdb pgbench./bin/pgbench

article thumbnail

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

HammerDB

compared to previous releases is that the workload names have changed from TPC-C and TPC-H to TPROC-C and TPROC-H respectively and therefore a key question is how are the v4.0 The simple answer is nothing, the workloads are exactly the same workloads derived from the TPC-C and TPC-H specifications and HammerDB v4.0

C++ 40