…here and from the Percona Software Repositories). Based on MySQL 5.5.22, including all the bug fixes … stable release in the 5.5 series. All of Percona‘s software is open-source and free, … Bugs Fixed: While running the test case found that MEMORY engine may return rows in non-deterministic order …
Comment: Benchmarking single-row insert performance on Amazon EC2
… it fits in main memory (and would have fit even with only a few GB of main memory). The cost of querying this database…-over/) on a newer version of iiBench showed that with 16GB of RAM, Inno hits the memory wall at about 100M rows, which….gz One of the advantages of the newer version of iiBench (the python version that Mark wrote http://bazaar.launchpad.net/~mdcallag/mysql-patch…
Post: Benchmarking single-row insert performance on Amazon EC2
… type with highest memory available, and memory is what really really matters. High-Memory Quadruple Extra Large Instance 68.4 GB of memory 26 EC2 Compute Units (8 virtual cores with 3.25 EC2 Compute Units each) 1690 GB of instance storage… software RAID 10. Now let’s come to the MySQL configuration. MySQL Configuration I used Percona Server 5.5.22-55 for…
Post: Troubleshooting MySQL Memory Usage
… exactly memory is allocated. This was not much of the problem in MySQL 3.23 when there would only handful of places where memory could… too. Memory Leaks There are many kinds of memory leaks and I would say these are rather rare in MySQL. Most suspected memory leaks end… future releases of MySQL, MariaDB or Drizzle bring improvements in this space allowing us to see directly for what purpose memory is allocated…
Post: Join Optimizations in MySQL 5.6 and MariaDB 5.5
… join optimizations when the workload fits entirely in memory. For the purpose of benchmarking in-memory workload, the InnoDB buffer pool size is… for MySQL 5.6 becomes approximately equal to that of MySQL 5.5. MariaDB 5.5 is quite slow as compared to both MySQL 5.5 and MySQL 5.6…
Post: Multi Range Read (MRR) in MySQL 5.6 and MariaDB 5.5
… Factor of 40 (InnoDB dataset size ~95G), because the query was taking far too long to execute, ~11 hours in case of MySQL 5.5 and ~5 hours in case of MySQL 5.6 and MariaDB 5.5. Note… MySQL 5.6, when the workload fits entirely in memory, because there is no extra cost for memory access at random locations versus memory…
Post: Index Condition Pushdown in MySQL 5.6 and MariaDB 5.5 and its performance impact
… in preparation for the talk comparing the optimizer enhancements in MySQL 5.6 and MariaDB 5.5. We are taking a… optimizer enhancement Index Condition Pushdown (ICP). Its available in both MySQL 5.6 and MariaDB 5.5 Now let’s take…
Post: Joining many tables in MySQL - optimizer_search_depth
… read less than 1000 rows and doing it completely in memory. The plan optimizer picked was very good one, yet you… number of tables. I was wondering if 0 is automatic selection why do we have value of 62 being default in MySQL 5… explanation somewhat conflicting though as if we assume MySQL users do not join lots of tables (less than 7) when using 0…
Post: Percona Server 5.5.21-25.1 released!
… are doing another release based on MySQL 5.5.21 as we have a couple of important bug fixes that we wish to make available. Bugs Fixed: Fixed a memory corruption regression introduced… warnings on CentOS 5. Bug fixed #962940 (Laurynas Biveinis). Fixed MySQL upstream bug #64160 that was causing issues on upgrade to…
Post: The Doom of Multiple Storage Engines
One of the big “Selling Points” of MySQL is support for Multiple Storage engines, and from the glance … Optimizer – such as in memory nature of MEMORY storage engine, clustering by Primary key in Innodb and distributed nature of NDB makes it more… very actively because of potential complications involved. Now lets think what we could have if we have a version of MySQL Server which…

