Remove Benchmarking Remove Best Practices Remove Code Remove Hardware
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. <code> 127.0.0.1:6379> <code> 127.0.0.1:6379>

Metrics 130
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. We had specializations in hardware, operating systems, databases, graphics, etc.

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

Further improved handling and reliability of OneAgent deployments

Dynatrace

Dynatrace OneAgent deployment and life-cycle management are already widely considered to be industry benchmarks for reliability and efficiency. Easier rollout thanks to log storage best practices. Easier rollout thanks to log storage best practices. Dynatrace news.

article thumbnail

HammerDB MySQL and MariaDB Best Practice for Performance and Scalability

HammerDB

This post complements the previous best practice guides this time with the focus on MySQL and MariaDB and achieving top levels of performance with the HammerDB MySQL TPC-C test. As is also the case this limitation is at the database level (especially the storage engine) rather than the hardware level.

article thumbnail

The Speed of Time

Brendan Gregg

The broken Java stacks turned out to be beneficial: They helped group together the os::javaTimeMillis() calls which otherwise might have have been scattered on top of different Java code paths, appearing as thin stacks everywhere. Without NMI, some kernel code paths (interrupts disabled) can't be profiled. But I'm not completely sure.

Speed 126
article thumbnail

The Ultimate Guide to Database High Availability

Percona

Defining high availability In general terms, high availability refers to the continuous operation of a system with little to no interruption to end users in the event of hardware or software failures, power outages, or other disruptions. If a primary server fails, a backup server can take over and continue to serve requests.

article thumbnail

The Speed of Time

Brendan Gregg

The broken Java stacks turned out to be beneficial: They helped group together the os::javaTimeMillis() calls which otherwise might have have been scattered on top of different Java code paths, appearing as thin stacks everywhere. Without NMI, some kernel code paths (interrupts disabled) can't be profiled.

Speed 52