… continuing series on the Star Schema Benchmark. In my previous blog post I compared MySQL 5.5.30 to MySQL 5.6.10, both with default settings… presents some unique challenge to the database optimizer. The SSB benchmark consists of four sets of queries. Each set is known… always performs better, at least for this workload. Notes MySQL version used: 5.6.11, custom compiled to remove performance_schema For the…
Post: Learn About MySQL 5.6 at the Percona Live MySQL Conference
April 3, 2013 By Leave a Comment
… on “Driving MySQL Innovation”. In addition, Oracle MySQL technologists will lead three breakout sessions on MySQL 5.6 at the Percona Live MySQL Conference: “MySQL 5.6: Performance Benchmarks, Tuning, and ‘Best’ Practices” by Dmitri Kravtchuk, MySQL Performance Architect “MySQL 5.6: What’s…
Post: trx descriptors: MySQL performance improvements in Percona Server 5.5.30-30.2
April 12, 2013 By 3 Comments
… case for read-only optimization in MySQL 5.6 and as you can see MySQL 5.6 shines in this benchmark. This is also the case that Oracle seems to focus the most in their MySQL 5.6 benchmarks. However, the “trx descriptors” optimization in Percona Server 5.5 is fairly close in terms of…
Post: MySQL 5.6 - InnoDB Memcached Plugin as a caching layer
March 29, 2013 By 10 Comments
… persistent cache can be invaluable. Enter MySQL 5.6 with the memcached plugin… As part of the standard MySQL 5.6 GA distribution, there is a… up the plugin: http://dev.mysql.com/doc/refman/5.6/en/innodb-memcached-setup.html As a quick benchmark, I ran some batches of fetch and store against both a standard memcached instance and a minimally tuned MySQL 5.6 instance…
Post: Percona Server for MySQL 5.5.30-30.2 now available
April 10, 2013 By 10 Comments
… Server for MySQL will now be shipped with the libjemalloc library. Benchmark showing the impact of memory allocators on MySQL performance can be…. Bug fixed #1163439 (Alexey Kopytov). Ported back from the upstream MySQL 5.6 the fix for unnecessary log_flush_order_mutex acquisition. Bug…
Post: MySQL and Percona Server in LinkBench benchmark
May 8, 2013 By 18 Comments
… run this benchmark, can be found here. We decided to run this benchmark for MySQL Server 5.5.30, 5.6.11 and Percona Server 5.5.30 and… the IO-bound scenario. Percona Server 5.5 outperforms MySQL in about 2x times. Both MySQL 5.5.30 and MySQL 5.6.11 demonstrate notable drops in performance…
Post: More on MySQL transaction descriptors optimization
April 26, 2013 By Leave a Comment
… 5.5.30-30.2 and a followup by Dimitri Kravchuk, we have received a large number of questions on why the benchmark…’s tests Percona Server scalability is somewhere in between of MySQL 5.5 and MySQL 5.6. In order to understand more about differences between results… much confusion. Even though the read-only transactions optimization in MySQL 5.6 virtually eliminates contention on the mutex protecting the list of…
Post: Keynotes, BOFs, and the Community Networking Reception at Percona Live MySQL Conference and Expo
April 15, 2013 By 1 Comment
… MySQL Sunny Bains, Senior Principal Software Engineer, Oracle Topic: “MySQL 5.6: What’s New in InnoDB” Dmitri Kravtchuk, MySQL Performance Architect, Oracle Topic: “MySQL 5.6: Performance Benchmarks, Tuning, and ‘Best’ Practices” Luís Soares, Senior Software Engineer, Oracle Topic: “MySQL 5.6: Redefining Replication…
Post: Why MySQL Performance at Low Concurrency is Important
March 27, 2013 By 8 Comments
… posts and articles look at MySQL performance starting with certain concurrency as the low point. For example, MySQL 5.6 DBA and Developer Guide… jobs are written to be single-threaded. MySQL replication is single-thread too, and MySQL 5.6 brings some abilities of parallel replication but… in real life with low concurrency. When it comes to benchmarks I would love to see results published starting from concurrency…
Post: Memory allocators: MySQL performance improvements in Percona Server 5.5.30-30.2
April 15, 2013 By
… – jemalloc helps MySQL 5.5.30 to fix issues with malloc scalability but still scanning of the transaction list causes performance drop = MySQL 5.6.10 – in autocommit mode 5.6.10 has no problem with transaction list scanning…
