June 18, 2013

Post: Memory allocators: MySQL performance improvements in Percona Server 5.5.30-30.2

1) memory allocation is an costly operation and if memory allocator has scalability problems (like allocator from glibc) this will notably slowdown MySQL…sysbench POINT_SELECT test for glibc and jemalloc allocators. Observations: = MySQL 5.5.30 – throughput of MySQL 5.5.30 with glibc is limited first…

Post: Virident vCache vs. FlashCache: Part 2

… 0.5 and the version of MySQL used was Percona Server 5.5.30-rel30.1-465. Each test was allowed to run for 7200 seconds, and… with a baseline HDD configuration for MySQL (configuration A, listed at the bottom of this post) and then tried three additional sets…-cache system is being crushed by IO wait. FlashCache and vCache both show improvements, but it’s not until we get to…

Post: Multi Range Read (MRR) in MySQL 5.6 and MariaDB 5.5

… 912318 Select_scan 1 1 1 1 1 Sort_scan 1 1 1 1 1 As you can see from the status counters above that both MySQL 5.6 and MariaDB 5.5 are reporting… is no difference in query times between MySQL 5.5 and MySQL 5.6/MariaDB 5.5 This is another area of improvement in the optimizer, as it is…

Post: Join Optimizations in MySQL 5.6 and MariaDB 5.5

…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. For MariaDB 5.5 … 6718351 6611675 6707882 5479445 5527245 Select_scan 1 1 1 1 1 1 Sort_scan 1 1 1 1 1 1 The first obvious improvement is shown by the high numbers …

Post: Can we improve MySQL variable handling ?

…(0.00 sec) mysql> select @@global.sort_buffer_size; +—————————+ | @@global.sort_buffer_size | +—————————+ | 2097152 | +—————————+ 1 row in set…SCHEMA.GLOBAL_VARIABLES Currently as of MySQL 5.5 it contains only variable name and value. Yet I would …

Post: MySQL 5.6.10 Optimizer Limitations: Index Condition Pushdown

… approximately 8 million of them having role_id = 1, and 266 have role_id = 1 and containing the word ‘Jaime’ somewhere in the field… is one of the new features of MySQL 5.6, and actually is a great improvement over MySQL 5.5. For example, in this case, the actual… MySQL 5.6 query optimization improvements in a practical way, with real-life examples? Do you want to know a 3-party, independent and

Post: How Percona does a MySQL Performance Audit

… all-in-one commands. For example, ‘top -n 1and ‘uptime’. That shows me what processes are running, …5 5 If you don’t know how to read these, there’s a full explanation in our book, High Performance MySQL… query is going to be possible to improve a lot, and a simple mental calculation can then tell …

Post: Scaling problems still exist in MySQL 5.5 and Percona Server 5.5

MySQL 5.5 and Percona Server 5.5 do not solve all scalability problems even for read only … Server 5.1.56-12.7 and Percona Server 5.5.11-20.2 with former being configured with innodb_buffer_pool_instances=16 and 400GB… is improvement from complete disaster to something absolutely unacceptable. If we look at the gain system shows from performance at 1 thread…

Post: InnoDB Full-text Search in MySQL 5.6 (part 1)

… InnoDB full-text search in MySQL 5.6 (part 1) in MySQL 5.6 is syntactically identical…that I used the community editions of MySQL 5.5.30 and MySQL 5.6.10 with no tuning …and the only page which appears to suggest how using an explicitly-defined column is done is this one, which discusses improving

Post: MySQL 5.5.8 - in search of stability

… to my post, MySQL 5.5.8 and Percona Server: being adaptive. I will refer to Dimitri’s article as article [1]. As always, Dimitri…. Article [1] recommends using the innodb_max_dirty_pages_pct and innodb_io_capacity parameters to get stable throughput in MySQL 5.5.8. Let… NOTPM. That is, by disabling the doublewrite area, we improved the result 1.55x times. As it seems hard for InnoDB to…