Why Choose Percona Server For MySQL? Tyler Duzan

Transcription

1 Why Choose Percona Server For MySQL? Tyler Duzan Product Manager

2 Who Am I? My name is Tyler Duzan Formerly an operations engineer for more than 12 years focused on security and automation Now a Product Manager at Percona Have been using MySQL in production for around 5 years 2

3 Outline 1. Bio & Outline 2. Percona Server for MySQL Overview Using Percona Server for MySQL Features Making The Choice 5. 3 What is Percona Server for MySQL? Comparing Percona Server for MySQL to MariaDB Server Comparing Percona Server for MySQL to MySQL Community Evaluating Your Use Case Open Source is About Choice Q&A

4 Percona Server for MySQL Overview

5 What is Percona Server for MySQL? First release in December 2008 Focused on performance and stability improvements layered on top of MySQL Community Edition Addresses a need for deeper diagnostics and performance tuning capabilities Provides a place to develop new storage engines and strategies 5 XtraDB developed as high performance drop-in replacement for InnoDB TokuDB focused on write-heavy workloads, supports fractal-tree indexes MyRocks focused on write-heavy workloads, supports LSM trees MySQL Enterprise features available in an open-source release Expedited bug fixes for Percona Support customers and shared with the community

6 What is Percona Server for MySQL? 6

7 Percona Server vs MariaDB Server Maintains drop-in compatibility with MySQL, while MariaDB Server has diverged Higher performance default configuration for out-of-the-box speed Contains all new MySQL features, including Group Replication MariaDB includes Galera Cluster as a plugin, Percona has been developing Percona XtraDB Cluster (PXC) since PXC is shipped as a special release of Percona Server for MySQL with a patched version of Galera built-in with numerous improvements and integration with ProxySQL

8 Percona Server vs MySQL Community MySQL Enterprise features without the licensing cost Extra Diagnostic Features Additional counters Improved SHOW and EXPLAIN commands Improved Performance 8 Thread Pooling PAM Authentication XtraDB Improved flushing and buffer pool scalability Additional configuration tunables Capability for compressed columns with dictionaries

9 Percona Server vs MySQL Community, Cont. Improved Stability and Security Additional Storage Engines 9 XtraBackup integrations and lightweight backup locks Ability to kill idle transactions Improved handling of corrupted tables Ability to enforce a specific storage engine for table creation TokuDB MyRocks (experimental)

10 Using Percona Server for MySQL Features

11 Extended SHOW INNODB ENGINE STATUS Part of the troubleshooting/informational improvements to MySQL Available in Percona Server for MySQL , , and or later Adds additional information and reorganizes the output of SHOW INNODB ENGINE STATUS In the log section Max checkpoint age, Checkpoint age target, Modified age, Checkpoint age In the buffer pool and memory section Internal Hash Tables, Buffer pool size in bytes In the row operations section Count of RW transactions occurring inside InnoDB Additionally lets the administrator control showing locks with the variable innodb_show_verbose_locks 11

12 MyRocks Storage Engine Experimental packages available starting with Based on RocksDB, added through joint effort of Percona and Facebook Facebook has migrated their entire user DB from InnoDB to MyRocks Compared to InnoDB, MyRocks is better optimized for write-heavy workloads by making use of LSM-tree based indexes Requires less storage space on disk by implementing more efficient on-disk format Is SSD storage optimized to increase storage endurance SSD storage optimizations also increase overall IO performance of the underlying storage due to different access patterns 12

13 MyRocks Storage Engine Below figures are all based on Mark Callaghan s Linkbench testing MyRocks uses 1/2 the space on disk of Compressed InnoDB MyRocks uses 1/3 the space on disk of Uncompressed InnoDB MyRocks insert performance doesn't degrade when the database is larger than memory For IO-Bound write workloads, MyRocks has almost double the insert rate of InnoDB Due to better IO efficiency, MyRocks shows an almost 1.5x increase in TPS compared to Compressed InnoDB 13

14 Enforcing the Storage Engine Available in Percona Server for MySQL and or later Is implemented as a variable which can be used for enforcing the use of a specific storage engine for table creation When this variable is specified and a user tries to create a table using an explicit storage engine that is not the specified enforced engine: If the NO_ENGINE_SUBSTITUTION SQL mode is enabled the user will receive an error If the NO_ENGINE_SUBSTITUTION SQL mode is disabled the user will receive a warning and the table will be created with the enforced engine in accordance with MySQL behavior with default engines This feature must be disabled before performing a mysql_upgrade There also is an optional utility user with admin access for DBaaS uses 14

15 Column Compression with Dictionaries Based on contributions from Pinterest in conjunction with Percona Available in Percona Server for MySQL and or later Makes use of the ZLIB compression library, same library as is used by InnoDB Page Compression in 5.7 Due to the ability to provide pre-defined dictionaries can be optimized for JSON Is a data-type modifier, so operates transparently and exists independently from user-level SQL or InnoDB compression. Causes the data stored in the column to be compressed on writing to storage and decompressed on reading. For all other purposes, the data type is identical to the one without the modifier 15

16 Column Compression with Dictionaries Supports being used with the following data types BLOB (including TINYBLOB, MEDIUMBLOB, LONGBLOG) TEXT (including TINYTEXT, MEDUUMTEXT, LONGTEXT) VARCHAR (including NATIONAL VARCHAR) VARBINARY JSON A few limitations due exist for which columns can be compressed Compressed columns cannot be used in indices (neither on their own nor as parts of composite keys). ALTER TABLE... DISCARD/IMPORT TABLESPACE is not supported for tables with compressed columns. 16

17 Column Compression with Dictionaries Data size, % 17

18 Column Compression with Dictionaries Query time, % 18

19 User Statistics Part of the troubleshooting/informational improvements in MySQL Feature contributed by Google and Percona Available in Percona Server for MySQL , , and or later This feature adds several INFORMATION_SCHEMA tables, several commands, and the userstat variable. The tables and commands can be used to understand the server activity better and identify the source of the load. It is disabled by default, and must be enabled by setting userstat to ON Works by keeping several hash tables in memory, so does incur some overhead. 19

20 User Statistics To avoid contention over global mutexes, each connection has its own local statistics, which are occasionally merged into the global statistics, and the local statistics are then reset to 0. Adds the following tables to INFORMATION_SCHEMA CLIENT_STATISTICS INDEX_STATISTICS TABLE_STATISTICS THREAD_STATISTICS USER_STATISTICS Provides FLUSH and SHOW commands for each of these tables These commands accept WHERE clauses, but ignore LIKE clauses 20

21 Making the Choice

22 Evaluating Your Use Case Do you need to maintain compatibility with MySQL for your application, such as migrating from an older version of MySQL? Do you prioritize performance with minimal tuning required? Percona Server is built with performance in mind, releasing performances fixes and new options. Default settings are more performant than those in MariaDB Server or MySQL Community Are you interested in new storage engines or have write-heavy workloads? 22 Percona Server or Oracle MySQL offer the better choice because of drop-in compatibility Percona Server is the primary point of development for TokuDB and MyRocks, both write-performance focused storage engines

23 Open Source is About Choice 23 Oracle MySQL, MariaDB Server, and Percona Server for MySQL are all great choices to use as the database for your application Percona is committed to supporting all three databases for our customers, including continued support for MariaDB as it diverges from MySQL Open source software is about choice, pick what is right for your use case whether that s Percona Server for MySQL or something else

24 Questions?

25 Thank You Sponsors! 25

26 SAVE THE DATE! April 23-25, 2018 Santa Clara Convention Center CALL FOR PAPERS OPENING SOON! 26