jorgenloland.blogspot.com
Jørgen's point of view: Favorite MySQL 5.6 features: an optimizer perspective
http://jorgenloland.blogspot.com/2012/12/favorite-mysql-56-features-optimizer.html
Jørgen's point of view. Mostly about the MySQL Optimizer. Monday, December 17, 2012. Favorite MySQL 5.6 features: an optimizer perspective. There are so many exciting new features in MySQL 5.6 that I almost don't know where to start. To mention a few, MySQL's multi-core scalability. Has been significantly improved to meet modern hardware, InnoDB has better index statistics. Replication has multi-threaded slaves. And global transaction identifiers. New ways to understand query plans:. Once and for all....
jorgenloland.blogspot.com
Jørgen's point of view: The MySQL range access method explained
http://jorgenloland.blogspot.com/2011/08/mysql-range-access-method-explained.html
Jørgen's point of view. Mostly about the MySQL Optimizer. Tuesday, August 23, 2011. The MySQL range access method explained. The range access method uses an index to read a subset of rows that form one or multiple continuous index value intervals. The intervals are defined by the query's range predicates, which are comparisons using any of =, = , IN(), IS NULL, IS NOT NULL, , , =, =, BETWEEN,! SELECT * FROM blog WHERE author id IN (1, 7, 8, 10). SELECT * FROM orders WHERE value 1000. Read row from table.
jorgenloland.blogspot.com
Jørgen's point of view: Index Condition Pushdown to the rescue!
http://jorgenloland.blogspot.com/2012/03/index-condition-pushdown-to-rescue.html
Jørgen's point of view. Mostly about the MySQL Optimizer. Monday, March 19, 2012. Index Condition Pushdown to the rescue! A while ago, I explained. How range access in a multiple-part index works and why MySQL can't utilize key parts beyond the first occurrence of some often used comparison operators. Luckily, there is a great improvement underway in MySQL 5.6 that will remedy much of this limitation. Meet Index Condition Pushdown. How does ICP work? That does not allow keypart 2,.,keypart n. With ICP en...
jorgenloland.blogspot.com
Jørgen's point of view: Gluh on InnoDB extended secondary keys
http://jorgenloland.blogspot.com/2012/12/gluh-on-innodb-extended-secondary-keys.html
Jørgen's point of view. Mostly about the MySQL Optimizer. Thursday, December 20, 2012. Gluh on InnoDB extended secondary keys. Sergey Glukhov (Gluh) recently wrote an interesting blog about InnoDB secondary key improvements in MySQL 5.6. His blog isn't aggregated to planet.mysql.com but certainly deserves some attention. Here it is: InnoDB, extended secondary keys. Subscribe to: Post Comments (Atom). MySQL Optimizer Team Blogs. Gluh on InnoDB extended secondary keys. Former MySQL Optimizer developer.
jorgenloland.blogspot.com
Jørgen's point of view: September 2013
http://jorgenloland.blogspot.com/2013_09_01_archive.html
Jørgen's point of view. Mostly about the MySQL Optimizer. Friday, September 13, 2013. Next MySQL mini-seminar in Trondheim October 17. We have the pleasure to announce that the next MySQL mini-seminar in Trondheim will be held on October 17 15:00-18:00. This time, MySQL Monitoring and performance schema evangelist Mark Leith will visit us. The agenda will be similar to last mini-seminar:. Presentation: MySQL monitoring and performance Schema,. Suggestions for presentations on future seminars.
jorgenloland.blogspot.com
Jørgen's point of view: FAQ: InnoDB extended secondary keys
http://jorgenloland.blogspot.com/2013/10/faq-innodb-extended-secondary-indexes.html
Jørgen's point of view. Mostly about the MySQL Optimizer. Monday, October 21, 2013. FAQ: InnoDB extended secondary keys. MySQL 5.6 introduced a new feature called extended secondary keys. We get a lot of questions about it and find that most of them come from a few incorrect assumption. In this post I'll try to get rid of the confusion once and for all. Famous last words. here goes:. Q1: Do I need to do anything to enable extended secondary keys? Q2: Does extended secondary keys only work with InnoDB?
jorgenloland.blogspot.com
Jørgen's point of view: Copying unused bytes is bad (duh!)
http://jorgenloland.blogspot.com/2012/04/copying-unused-bytes-is-bad-duh.html
Jørgen's point of view. Mostly about the MySQL Optimizer. Wednesday, April 18, 2012. Copying unused bytes is bad (duh! Last summer my colleague Marko Mäkelä committed this seemingly innocent performance fix for InnoDB in MySQL 5.6:. 3581 Marko Makela 2011-08-10. Bug#12835650 VARCHAR maximum length performance impact. Row sel field store in mysql format(): Do not pad the unused part of. The buffer reserved for a True VARCHAR column (introduced in 5.0.3). Oh my were we up for a ride! The MySQL server used ...
jorgenloland.blogspot.com
Jørgen's point of view: On queries with many values in the IN clause
http://jorgenloland.blogspot.com/2012/04/on-queries-with-many-values-in-in.html
Jørgen's point of view. Mostly about the MySQL Optimizer. Tuesday, April 10, 2012. On queries with many values in the IN clause. This is what the help text has to tell about the variable:. The optimizer will use existing index statistics instead of doing index dives for equality ranges if the number of equality ranges for the index is larger than or equal to [the value of variable]. If set to 0, index dives are always used. Equality range" means predicates using operators IN() or =. Mysql SELECT * FROM m...
jorgenloland.blogspot.com
Jørgen's point of view: DBT-3 Q3: 6 x performance in MySQL 5.6.10
http://jorgenloland.blogspot.com/2013/02/dbt-3-q3-6-x-performance-in-mysql-5610.html
Jørgen's point of view. Mostly about the MySQL Optimizer. Wednesday, February 13, 2013. DBT-3 Q3: 6 x performance in MySQL 5.6.10. However, some access methods can only be considered after the join order has been decided and therefore gets special treatment in the MySQL optimizer. For join conditions, e.g. "WHERE table1.col1 = table2.col2". The following database schema will be used:. Order id INT PRIMARY KEY,. Cust id INT,. INDEX cid (cust id). ENGINE = InnoDB;. Cust id INT PRIMARY KEY,. ENGINE = InnoDB;.
jorgenloland.blogspot.com
Jørgen's point of view: October 2013
http://jorgenloland.blogspot.com/2013_10_01_archive.html
Jørgen's point of view. Mostly about the MySQL Optimizer. Monday, October 21, 2013. FAQ: InnoDB extended secondary keys. MySQL 5.6 introduced a new feature called extended secondary keys. We get a lot of questions about it and find that most of them come from a few incorrect assumption. In this post Ill try to get rid of the confusion once and for all. Famous last words. here goes:. Q1: Do I need to do anything to enable extended secondary keys? Q2: Does extended secondary keys only work with InnoDB?