Comments on: Join performance of MyISAM and Innodb http://www.mysqlperformanceblog.com/2006/05/29/join-performance-of-myisam-and-innodb/ Percona's MySQL & InnoDB performance and scalability blog Sat, 11 Feb 2012 16:45:54 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Jatin Mehta http://www.mysqlperformanceblog.com/2006/05/29/join-performance-of-myisam-and-innodb/comment-page-1/#comment-742815 Jatin Mehta Sat, 03 Apr 2010 08:56:55 +0000 http://www.mysqlperformanceblog.com/2006/05/29/join-performance-of-myisam-and-innodb/#comment-742815 QUERY: SELECT SQL_CALC_FOUND_ROWS p.*, FLOOR(p.prodratingtotal/p.prodnumratings) AS prodavgrating, 0 AS prodgroupdiscount, pi.* , (IF(p.prodname='gold', 10000, 0) + IF(p.prodcode='gold', 10000, 0) + ((MATCH (ps.prodname) AGAINST ('gold')) * 10) + MATCH (ps.prodname,ps.prodcode,ps.proddesc,ps.prodsearchkeywords) AGAINST ('gold')) AS score FROM products p LEFT JOIN product_images pi ON (p.productid = pi.imageprodid AND pi.imageisthumb = 1) INNER JOIN product_search ps ON p.productid = ps.productid WHERE p.prodvisible = 1 AND (ps.prodcode = 'gold' OR TRUE) AND (MATCH (ps.prodname,ps.prodcode,ps.proddesc,ps.prodsearchkeywords) AGAINST ('gold')) ORDER BY score DESC LIMIT 20 EXECUTION TIME: 2.5000+ seconds TABLES DATA: products: 31,000 records product_images: 92,000 records product_search: 57,000 records EXPLAIN COMMAND WITH ABOVE QUERY: 1 SIMPLE ps fulltext prodname prodname 0 1 Using where; Using temporary; Using filesort 1 SIMPLE p eq_ref PRIMARY,i_products_rating_vis,i_products_added_vis,i_products_sortorder_vis PRIMARY 4 shoppingcart_5521.ps.productid 1 Using where 1 SIMPLE pi ref i_product_images_imageprodid i_product_images_imageprodid 5 shoppingcart_5521.p.productid,const 1 QUERY:
SELECT SQL_CALC_FOUND_ROWS p.*, FLOOR(p.prodratingtotal/p.prodnumratings) AS prodavgrating, 0 AS prodgroupdiscount, pi.* , (IF(p.prodname=’gold’, 10000, 0) + IF(p.prodcode=’gold’, 10000, 0) + ((MATCH (ps.prodname) AGAINST (‘gold’)) * 10) + MATCH (ps.prodname,ps.prodcode,ps.proddesc,ps.prodsearchkeywords) AGAINST (‘gold’)) AS score FROM products p LEFT JOIN product_images pi ON (p.productid = pi.imageprodid AND pi.imageisthumb = 1) INNER JOIN product_search ps ON p.productid = ps.productid WHERE p.prodvisible = 1 AND (ps.prodcode = ‘gold’ OR TRUE) AND (MATCH (ps.prodname,ps.prodcode,ps.proddesc,ps.prodsearchkeywords) AGAINST (‘gold’)) ORDER BY score DESC LIMIT 20

EXECUTION TIME: 2.5000+ seconds

TABLES DATA:
products: 31,000 records
product_images: 92,000 records
product_search: 57,000 records

EXPLAIN COMMAND WITH ABOVE QUERY:
1 SIMPLE ps fulltext prodname prodname 0 1 Using where; Using temporary; Using filesort
1 SIMPLE p eq_ref PRIMARY,i_products_rating_vis,i_products_added_vis,i_products_sortorder_vis PRIMARY 4 shoppingcart_5521.ps.productid 1 Using where
1 SIMPLE pi ref i_product_images_imageprodid i_product_images_imageprodid 5 shoppingcart_5521.p.productid,const 1

]]> By: InnoDB is better for SugarCRM - Blog of Leonid Mamchenkov http://www.mysqlperformanceblog.com/2006/05/29/join-performance-of-myisam-and-innodb/comment-page-1/#comment-339564 InnoDB is better for SugarCRM - Blog of Leonid Mamchenkov Sun, 03 Aug 2008 20:51:13 +0000 http://www.mysqlperformanceblog.com/2006/05/29/join-performance-of-myisam-and-innodb/#comment-339564 [...] similarly brief Google search suggested (see here and here) and explained converting MySQL tables from MyISAM to InnoDB.  A test has been performed and [...] [...] similarly brief Google search suggested (see here and here) and explained converting MySQL tables from MyISAM to InnoDB.  A test has been performed and [...]

]]> By: peter http://www.mysqlperformanceblog.com/2006/05/29/join-performance-of-myisam-and-innodb/comment-page-1/#comment-1558 peter Mon, 07 Aug 2006 16:05:21 +0000 http://www.mysqlperformanceblog.com/2006/05/29/join-performance-of-myisam-and-innodb/#comment-1558 Feel fee to test it Stefan :) Generally for join the table which gets random lookup is more important - table which is having full table scan or range scan contributes less to total prformance. So in our case performance will be similar to join of two Innob tables. ...Also no locks will be happening. Innodb does not lock rows for normal selects, consistent reads are used instead. Feel fee to test it Stefan :)

Generally for join the table which gets random lookup is more important – table which is having full table scan or range scan contributes less to total prformance.

So in our case performance will be similar to join of two Innob tables.

…Also no locks will be happening. Innodb does not lock rows for normal selects, consistent reads are used instead.

]]> By: stefan minka` http://www.mysqlperformanceblog.com/2006/05/29/join-performance-of-myisam-and-innodb/comment-page-1/#comment-1555 stefan minka` Mon, 07 Aug 2006 10:30:56 +0000 http://www.mysqlperformanceblog.com/2006/05/29/join-performance-of-myisam-and-innodb/#comment-1555 how different becomes the situation, when a join both myisam and innodb tables together. exampe: - table a is myisam, table b is innodd - select ... from a inner join b on a.x=b.x additional question: lets assume both tables will be big, so will the table b (innodb) be locked by row, or as whole? how different becomes the situation, when a join both myisam and innodb tables together.

exampe:
- table a is myisam, table b is innodd
- select … from a inner join b on a.x=b.x

additional question: lets assume both tables will be big, so will the table b (innodb) be locked by row, or as whole?

]]> By: MySQL Developer » Blog Archive » MyISAM to InnoDB http://www.mysqlperformanceblog.com/2006/05/29/join-performance-of-myisam-and-innodb/comment-page-1/#comment-1075 MySQL Developer » Blog Archive » MyISAM to InnoDB Sun, 16 Jul 2006 16:13:50 +0000 http://www.mysqlperformanceblog.com/2006/05/29/join-performance-of-myisam-and-innodb/#comment-1075 [...] Join Performance of MyISAM and InnoDB [via Planet MySQL] [...] [...] Join Performance of MyISAM and InnoDB [via Planet MySQL] [...]

]]>