PERFORMANCE_SCHEMA in MySQL 5.6: The Good, the Bad and the Ugly
12 November 4:00pm - 4:50pm @ Orchard 1
50 minutes conference
The list of new features and improvements to PERFORMANCE_SCHEMA in MySQL 5.6 is impressive: - Instrumentation for table input and output - Event filtering by table, based on schema and/or table names - Event filtering by thread. More information is collected for threads - Summary tables for table and index I/O, and for table locks - Instrumentation for statements and stages within statements - Configuration of instruments and consumers at server startup (not only at runtime) and it really becomes more a useful tool than a proof of concept (as it was in MySQL 5.5). In this session I'd like to concentrate on new features, features still missing, bugs, performance implications and use cases for PERFORMANCE_SCHEMA in MySQL 5.6. Discussion of the need for PERFORMANCE_SCHEMA and alternative approaches to find out the reasons of bottlenecks and performance problems is also planned.
Principal Support Engineer, Percona
Valerii joined Percona in September 2012 as a Principal Support Engineer. Before that Valerii worked in the Bugs Verification group of MySQL Support team at MySQL AB/Sun/Oracle for more than seven years. During all this time he processed bugs at http://bugs.mysql.com. He had also worked on complex support issues, coordinated cooperation of MySQL Support with optimizer, GUI tools and some other development teams. Later he was also responsible for decision making from Support side on bug fixing in all MySQL GA versions. Before joining MySQL AB Valerii worked as software developer, trainer, system administrator and DBA for Oracle and Informix databases. Valerii got a degree in Mathematics from the Moscow State University back in 1992. He currently lives with his family in the small town of Vyshgorod near Kyiv, Ukraine.