June 19, 2013

Post: MySQL and the SSB - Part 2 - MyISAM vs InnoDB low concurrency

May 22, 2013 By Leave a Comment

…. In my previous blog post I compared MySQL 5.5.30 to MySQL 5.6.10, both with default settings using… test. All OS caches are dropped at this time as well. These set of queries were tested on… be good for raw performance, but there are limitations which MyISAM imposes that are difficult to work with…

Filed Under: Benchmarks, MySQL Tagged With: , , , , , , ,

Post: More on MySQL transaction descriptors optimization

April 26, 2013 By Leave a Comment

… transaction optimization in MySQL 5.6, because all SELECT queries in the AUTOCOMMIT mode…MySQL 5.6 virtually eliminates contention on the mutex protecting the list of transactions, its applicability is quite limited… max_connections=5000 table_open_cache=5000 query_cache_type=OFF performance_schema=0…

Filed Under: Benchmarks, MySQL Tagged With: ,

Post: MySQL 5.5 and MySQL 5.6 default variable values differences

February 21, 2013 By 8 Comments

… | | BASEDIR | /mnt/nfs/dist/5.5.30 | /mnt/nfs/dist/5.6.10 | | BACK_LOG | 50 | 80 | | OPEN_FILES_LIMIT | 1024 | 5000 | | INNODB_AUTOEXTEND… differently now. The query_cache_type is now off by default with default size of 1MB while in MySQL 5.5 and before it was “ON” by default with query cache size of 0 which makes it disabled. I wish query_cache_size…

Filed Under: Insight for DBAs, MySQL Tagged With: , , ,

Post: MySQL Query Cache

July 27, 2006 By 70 Comments

…Query Cache Query Cache Status Query Cache Configuration I would just mention couple of points – as protection from one query wiping your all query cache option query_cache_limit was implemented which limits…

Filed Under: Insight for DBAs Tagged With:

Post: Join Optimizations in MySQL 5.6 and MariaDB 5.5

April 4, 2012 By 4 Comments

…query cache is disabled during these benchmark runs and that the disks are 4 5…order by revenue desc, o_orderdate LIMIT 10; In-memory workload …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 the query…

Filed Under: Benchmarks, Insight for DBAs, MySQL Tagged With: , , , , , , , , , , , , , ,

Post: Should we give a MySQL Query Cache a second chance ?

April 10, 2011 By 64 Comments

… same “cheat” as MySQL 5.5 uses for Innodb Buffer Pool and have multiple MySQL Query Cache instances hashed by query hash. It would help … query syntax may be hard. Query Cache Storage Engines MySQL Query Cache now stores queries in local memory, which is great however memory amount might be limited…

Filed Under: Insight for DBAs, MySQL

Post: Review of MySQL 5.6 Defaults Changes

October 8, 2012 By 10 Comments

… great summary of defaults changes in MySQL 5.6 compared to MySQL 5.5 In general there are a … provide as MySQL is typically protected by Firewall to begin with. open_files_limit = 5000 strangely… or even more would be good default. query_cache_size = 1M Query cache remains off by default but default …

Filed Under: Insight for DBAs, MySQL

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

March 21, 2012 By 10 Comments

…, ~11 hours in case of MySQL 5.5 and ~5 hours in case of MySQL 5.6 and MariaDB 5.5. Note that query cache is disabled during these benchmark runs and that the disks are 4 5.4K…, n_name, c_address, c_comment order by revenue desc LIMIT 20; In-memory workload Now let’s see how effective…

Filed Under: Benchmarks, Insight for DBAs, MySQL Tagged With: , , , , , , , , , , , , , ,

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

February 26, 2013 By 1 Comment

…I used the community editions of MySQL 5.5.30 and MySQL 5.6.10 with no tuning whatsoever…—-. 1 mysql mysql 98304 Feb 20 16:09 FTS_00000000000000ad_DELETED_CACHE.ibd -rw-rw—-. 1 mysql mysql …) mysql> delete from dir_test_innodb LIMIT 200000; Query OK, 200000 rows affected (8.65 sec) mysql> optimize…

Filed Under: Insight for DBAs, Insight for Developers, MySQL Tagged With: , , , , ,

Post: Index Condition Pushdown in MySQL 5.6 and MariaDB 5.5 and its performance impact

March 12, 2012 By 12 Comments

… preparation for the talk comparing the optimizer enhancements in MySQL 5.6 and MariaDB 5.5. We are taking a look at and benchmarking… Index Condition Pushdown (ICP). Its available in both MySQL 5.6 and MariaDB 5.5 Now let’s take a look briefly at what…. Index Condition Pushdown Traditional B-Tree index lookups have some limitations in cases such as range scans, where index parts after…

Filed Under: Benchmarks, Insight for DBAs, MySQL Tagged With: , , , , , , ,
« Older Posts