Percona white papers present information on a variety of topics, such as in-depth analyses and recommendations for common issues faced by database developers and administrators. The results of our benchmarking tests on software and hardware solutions are also presented. Where appropriate, Percona white papers present best practice recommendations that are based on our in-depth experience developed through working with leading technology users.
Will your database performance meet your business growth needs?
Today, keeping your enterprise agile and flexible is not just an advantage, it is a requirement.
We created a checklist of common but deadly MySQL problems to make your life easier. If handled reactively, these issues can lead to unacceptable downtime, unnecessary costs, malicious attacks, frustrated users, and lost business.
Backup and recovery processes are a foundational piece of any application infrastructure. A well-tested backup and recovery system can be the difference between a minor outage and the end of a business.
ScaleArc hired Percona to perform various tests on its database traffic management product. This case study is the outcome of the benchmarks carried out by Uday Sawant (ScaleArc) and Peter Boros (Percona).
This document represents current MySQL high availability best practices. These form the core of what Percona consultants and engineers will typically discuss with customers exploring this space.
The goal of this benchmark is to show the performance impact of using an Intel 520 SSD drive under a MySQL workload.
The TCP network traffic conversation between a client and a MySQL server is a rich source of data for many types of analysis. In this paper, we show how the simplest type of traffic packet headers with no payload can provide a surprising variety of information about the system’s performance. The techniques that we demonstrate are quick, require o
The goal of this research is to compare the performance (throughput) of Virident FlashMAX M1400 card with Fusion-io ioDrive Duo 1.28TB card under a tpcc-mysql workload.
Everyone wants to prevent database downtime by being proactive, but are
measures such as inspecting logs and analyzing SQL really proactive? Although
these are worthwhile, they almost always identify problems that already exist.
To be truly proactive, one must prevent problems, which requires studying and
understanding the reasons for downtime. T
