Remove Benchmarking Remove Cache Remove Testing Remove Tuning
article thumbnail

PostgreSQL Performance Tuning: Optimizing Database Parameters for Maximum Efficiency

Percona

Out of the box, the default PostgreSQL configuration is not tuned for any particular workload. It is primarily the responsibility of the database administrator or developer to tune PostgreSQL according to their system’s workload. What is PostgreSQL performance tuning? Why is PostgreSQL performance tuning important?

Tuning 52
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. Cache Hit Ratio The cache hit ratio represents the efficiency of cache usage.

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

The Most Important MySQL Setting

Percona

If we were to select the most important MySQL setting, if we were given a freshly installed MySQL or Percona Server for MySQL and could only tune a single MySQL variable, which one would it be? The throughput didn’t double but increased by 57%. The throughput didn’t double but increased by 57%. Are these results good enough?

Tuning 135
article thumbnail

The evolution of single-core bandwidth in multicore processors

John McCalpin

For most high-end processors these values have remained in the range of 75% to 85% of the peak DRAM bandwidth of the system over the past 15-20 years — an amazing accomplishment given the increase in core count (with its associated cache coherence issues), number of DRAM channels, and ever-increasing pipelining of the DRAMs themselves.

article thumbnail

Tuning PostgreSQL Database Parameters to Optimize Performance

Percona

Out of the box, the default PostgreSQL configuration is not tuned for any particular workload. It is primarily the responsibility of the database administrator or developer to tune PostgreSQL according to their system’s workload. This parameter sets how much dedicated memory will be used by PostgreSQL for cache. wal_buffers.

Tuning 56
article thumbnail

Evaluating the Evaluation: A Benchmarking Checklist

Brendan Gregg

A co-worker introduced me to Craig Hanson and Pat Crain's performance mantras, which neatly summarize much of what we do in performance analysis and tuning. These have inspired me to summarize another performance activity: evaluating benchmark accuracy. If the benchmark reported 20k ops/sec, you should ask: why not 40k ops/sec?

article thumbnail

How to Assess MySQL Performance

HammerDB

Therefore, before we attempt to measure our database performance, we should know the system or cloud instance to be tested in detail. Benchmarking the target Two of the more popular database benchmarks for MySQL are HammerDB and sysbench. For the experiments in this blog, we did not tune the system. 4.22 %usr 38.40