… talk comparing the optimizer enhancements in MySQL 5.6 and MariaDB 5.5. We are taking a look at and benchmarking optimizer enhancements one by one… aimed at a new optimizer enhancement Index Condition Pushdown (ICP). Its available in both MySQL 5.6 and MariaDB 5.5 Now let’s take… WHERE condition defined as: l_partkey = x and l_quantity >= 1 and l_quantity = 1 and l_quantity
Post: Index Condition Pushdown in MySQL 5.6 and MariaDB 5.5 and its performance impact
March 12, 2012 By 12 Comments
Post: Multi Range Read (MRR) in MySQL 5.6 and MariaDB 5.5
March 21, 2012 By 10 Comments
…performing the benchmark on IO bound workload, mentioned above. Counter Name MySQL 5.5 MySQL 5.6 MySQL 5.6 w/ read_rnd_bufer_size=4M MariaDB 5.5 MariaDB 5.5…
Post: Join Optimizations in MySQL 5.6 and MariaDB 5.5
April 4, 2012 By 2 Comments
…the talk comparing the optimizer enhancements in MySQL 5.6 and MariaDB 5.5. This blog post is … 6707882 5479445 5527245 Select_scan 1 1 1 1 1 1 Sort_scan 1 1 1 1 1 1 The first obvious improvement is …performance. I did not find much of a performance improvement from using Hash Join in MariaDB 5.5…
Post: Troubleshooting MySQL Upgrade Performance Regressions
February 15, 2012 By Leave a Comment
… lets say you upgraded from MySQL 5.1 to Percona Server 5.5 and instead of expected performance improvement you see your performance being worse. What should…through MySQL support channel if often helps to know whenever it is the problem in stick MySQL changes between versions on Percona enhancements…
Post: XtraDB storage engine release 1.0.2-2 (New Year edition)
December 29, 2008 By 20 Comments
… announce release 1.0.2-2 of our XtraDB storage engine. Here is a list of enhancements: split-…no enough free buffers. It helps if you have performance drops when data does not fit in memory. …in into MySQL-5.1.30 RPM as separated shared library, to use as drop-in plugin for existing MySQL-5.1.30 …
Post: XtraDB storage engine release 1.0.2-3 (Spring edition) codename Sapporo
March 2, 2009 By 10 Comments
… we announce release 1.0.2-3 of our XtraDB storage engine. Here is a list of enhancements: Move to MySQL 5.1.31 Scalability… work after MySQL 5.0 with binlog. We pretend to fix this and added “innodb_enable_unsafe_group_commit=[0|1]” parameter. Note….g. SSD or enough Write-Buffered), 0 may show better performance. Changed parameter for control read ahead activity. Now it accepts…
Post: Announcing Percona XtraDB Storage Engine: a Drop-in Replacement for Standard InnoDB
December 16, 2008 By 25 Comments
… of other features useful in high performance environments. Percona XtraDB includes all of… list of new features and enhancements: INFORMATION_SCHEMA.XTRADB_ENHANCEMENTS. This table contains information… MySQL-5.1.30 installation http://www.percona.com/mysql/5.1.30/binary/percona-xtradb-1.0.2-1-5.1…
Post: XtraDB: The Top 10 enhancements
August 13, 2009 By 5 Comments
… with the top 10 enhancements that XtraDB has over the built-in InnoDB included in MySQL 5.0 and 5.1. Building this list… workloads first: CPU scalability fixes – XtraDB improves performance on systems with multi-cpus (see docs 1, 2). Import/Export Tables – XtraDB allows… log files (innodb_log_file_size), which is worse for performance.  In a simple test, XtraDB recovered ten times faster…
Post: Heikki Tuuri answers to Innodb questions, Part II
November 4, 2007 By 13 Comments
… loss of performance with 5.0.X. I’m hopeful that 5.1.X will be better, but still not sure. HT: 5.0.xx… be better than 4.1.xx. PZ: I should note MySQL 5.0 vs 4.1 has a lot of performance differences and not all… working on the performance enhancement requests. It takes time for the patches to mature. We improved the scalability of InnoDB-5.0.30…
Comment: New MySQL Community Release Policies published
November 8, 2007 By 9 Comments
… this: http://bugs.mysql.com/bug.php?id=28591 does not count as a “BUG”. It was a performance enhancement. Those go into the next development version (5.1? 6.0?) No way should such a change be applied to 5.0…. This causes people to not trust the community versions of MySQL because they can’t be sure a simple update won…
