June 19, 2013

Comment: MySQL and Percona Server in LinkBench benchmark

One more bug that explains why LRU page flushing rate is much less than innodb_lru_scan_depth even if innodb_lru_scan_depth is large enough. Apparently fixed in 5.6.12 — http://bugs.mysql.com/bug.php?id=69170

Comment: Be careful when joining on CONCAT

Titan, the short answer is No. You could probably craft something, but it’s not going to be something as simple as EXPLAIN SOURCE. Aurimas

Comment: Be careful when joining on CONCAT

Hi there! Is there any ways to EXPLAIN the SQL which is imported from the SOURCE command! @@

Post: More on MySQL transaction descriptors optimization

… one aspect of the descriptors optimization that I thought was explained in the original post, but seems to cause much confusion…

Post: How to recover table structure from InnoDB dictionary

… (`INDEX_ID`,`POS`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 Fields names explain their content. Index id in our example is 1679: mysql…

Post: The write cache: Swap insanity tome III

… the physical cpus, the sockets and not cores. Jeremy Cole explained this here and here. In summary, you need to interleave…

Post: Rotating MySQL slow logs safely

… LOGS; These options should be equivalent, but MySQL bug 65481 explains that the HUP signal also flushes tables in addition to…

Comment: Testing the Micron P320h

…_DIRECT, while XFS not at all. This may also probably explain why there is near no difference on OLTP @EXT4 results…

Comment: Testing the Micron P320h

Has anyone explained why performance can be a lot better with EXT4?

Comment: Using index for ORDER BY vs restricting number of rows.

… order by NUM desc limit 5 Follow was index。 the explain: type:index,Extra:Using index; Using temporary; Using filesort i…