Remove 2018 Remove Benchmarking Remove Performance Testing Remove Virtualization
article thumbnail

Percona Database Performance Blog 2018 Year in Review: Top Blog Posts

Percona

Let’s look at some of the most popular Percona Database Performance Blog posts in 2018. With the Percona Database Performance Blog, Percona staff and leadership work hard to provide the open source community with insights, technical support, predictions and metrics around multiple open source database software technologies.

article thumbnail

Have You Tested Your App Performance & Capacity Recently?

Apica

million Netflix users as of Q3 2018. The Apica LoadTest solution uses innovative technologies like monitoring nodes and load clusters to reliably deliver and sustain a large-scale load of virtual users (VUs) to Hollywood for different, realistic user scenarios all at the same time.

Testing 40
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 MySQL and MariaDB Best Practice for Performance and Scalability

HammerDB

InnoDB is the storage engine that will deliver the best OLTP throughput and should be chosen for this test. . For anyone benchmarking MySQL with HammerDB it is important to understand the differences from sysbench workloads as HammerDB is targeted at a testing a different usage model from sysbench. c_ytd_payment: 10.00

article thumbnail

KPTI/KAISER Meltdown Initial Performance Regressions

Brendan Gregg

I then analyzed performance during the benchmark ([active benchmarking]), and used other benchmarks to confirm findings. Plotting the percent performance loss vs syscall rate per CPU, for my microbenchmark: Applications that have high syscall rates include proxies, databases, and others that do lots of tiny I/O.

article thumbnail

KPTI/KAISER Meltdown Initial Performance Regressions

Brendan Gregg

I then analyzed performance during the benchmark ([active benchmarking]), and used other benchmarks to confirm findings. Plotting the percent performance loss vs syscall rate per CPU, for my microbenchmark: Applications that have high syscall rates include proxies, databases, and others that do lots of tiny I/O.