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

Crucial Redis Monitoring Metrics You Must Watch

Scalegrid

Key metrics like throughput, request latency, and memory utilization are essential for assessing Redis health, with tools like the MONITOR command and Redis-benchmark for latency and throughput analysis and MEMORY USAGE/STATS commands for evaluating memory. This plays a crucial role in supervising the replication process.

Metrics 130
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

An analysis of performance evolution of Linux’s core operations

The Morning Paper

For the rest of us, if you really need that extra performance (maybe what you get out-of-the-box or with minimal tuning is good enough for your use case) then you can upgrade hardware and/or pay for a commercial license of a tuned distributed (RHEL). A second takeaway is this: security has a cost! Measuring the kernel. Headline results.

article thumbnail

How to Assess MySQL Performance

HammerDB

GHz 4th Generation Intel Xeon Scalable processors (code-named Sapphire Rapids) Up to 20% higher compute performance than z1d instances Up to 50 Gbps of networking speed Up to 40 Gbps of bandwidth to the Amazon Elastic Block Store (EBS) We can also verify these capabilities by running some simple benchmarks on the different subsystems.

article thumbnail

PostgreSQL Performance Tuning: Optimizing Database Parameters for Maximum Efficiency

Percona

Key areas include: Configuration parameter tuning : This tuning involves altering variables such as memory allocation, disk I/O settings, and concurrent connections based on specific hardware and requirements. Throughput: The throughput of an application is directly influenced by the speed at which the database can process and serve queries.

Tuning 52
article thumbnail

MySQL Performance Tuning 101: Key Tips to Improve MySQL Database Performance

Percona

This results in expedited query execution, reduced resource utilization, and more efficient exploitation of the available hardware resources. A finely tuned database processes queries more efficiently, leading to swifter results. MySQL relies heavily on the availability of hardware resources to perform at its best.

Tuning 52
article thumbnail

Compress objects, not cache lines: an object-based compressed memory hierarchy

The Morning Paper

Looking across a set of eight Java benchmarks, we find that only two of them are array dominated, the rest having between 40% to 75% of the heap footprint allocated to objects, the vast majority of which are small. Consider a B-Tree node from the B-tree Java benchmark: Uncompressed, it’s memory layout looks like (a) below. Evaluation.

Cache 61