Looking for an HA Solutions for your MySQL Database?

1. XtraDB Cluster
High-Performance High Availability Solution
Percona XtraDB Cluster integrates Percona Server and Percona
XtraBackup with the Codership Galera library of MySQL high
availability solutions in a single package.
In our latest release of Percona XtraDB Cluster, we’ve introduced
major performance improvements to the MySQL write-set
replication layer.
Up to 10 times better performance
Better instrumentation of Flow Control status
Instrumentation of Incremental State Transfer (IST)
Parallel State Transfer support with Percona XtraBackup
transactionspersecond,tpstransactionspersecond,tps Threads
Workload Improvements from Previous Version
Benchmarks use a three-node setup, connected via a 10GB network,
with sysbench load directed to one primary node.
Sysbench: dataset 100 tables / 4M rows (100GB)
Configuration:
- innodb_buffer_pool=150GB
- innodb_doublewrite=1
- innodb_flush_log_at_trx_commit=1
- sync_binlog=0/1
Box: 28 Cores + HT
HIGH PERFORMANCE
HIGH AVAILABILITY SOLUTION
Percona XtraDB Cluster: 5.7.16 5.7.17
Threads
sync_binlog=1

2. XtraDB Cluster
The most recent release of Percona XtraDB Cluster is
tuned for better scaling, and fast enough for the growing
demands of your applications.
Contact Us Now
To help you with your high availability database
environment, contact us at +1-888-316-9775 (USA), +44
203 608 6727 (Europe) or sales@percona.com.
Percona XtraDB Cluster Optimizations
HIGH PERFORMANCE
HIGH AVAILABILITY SOLUTION
Performance vs. Other Solutions
See how Percona XtraDB Cluster performs against other HA solutions.
transactionspersecond,tpstransactionspersecond,tps
Threads
Server: MariaDB
10.2.5RC
flow_control
100
MySQL+GR
5.7.17
flow_control
100
PerconaXtraDB
Cluster 5.7.17
flow_control
100
MySQL+GR
5.7.17
flow_control
default:25000
Sysbench: dataset 100 tables / 4M rows (100GB)
Configuration:
- innodb_buffer_pool=150GB
- innodb_doublewrite=1
- innodb_flush_log_at_trx_commit=1
- sync_binlog=0/1
Box: 28 Cores + HT
Threads
Splits the replication pre-commit hook into two explicit actions:
replicate (add write-set to group-channel) + pre-commit (enter
commit-monitor).
Releases the Commit Monitor once the transaction is successfully
added to the flush-stage of group-commit via new “interim-commit”
-- MySQL takes it from there.
Releases the Commit Monitor just before the REDO flush stage kicks
in, with accuracy ensured due to the REDO log flush persisting the
data sequentially.