June 19, 2013

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

of rows must be joined together (Q4.1, Q4.2) but worse when small amounts of data are examined. Conclusion In some cases MyISAMno caching of data at the filesystem level. The InnoDB indexes were built using ALTER TABLE fast index creation (merge sort). For the MyISAM

Post: InnoDB vs MyISAM vs Falcon benchmarks - part 1

…. We hope the performance of LIMIT queries will be fixed before release. MyISAM shows stable result. InnoDB is better than MyISAM by 58% in… big weakness of Falcon, as ‘using index‘ is very common optimization we use in our practice. READ_KEY_POINT_NO_DATA_LIMIT Query: SELECT… query performs a scan of all million rows. InnoDB is better than MyISAM by ~30% with 4-16 threads, but MyISAM scales a bit…

Post: How much overhead is caused by on disk temporary tables

… key blocks from temporary table index, so we get a lot of key writes which kill …writes | 0 | +————————+———+ 7 rows in set (0.00 sec) As you can see we have no writes because…MyISAM results. For 4M of rows mysql> select count(*) cnt,c from gtest group by c order by null limit 10…

Post: MyISAM Scalability and Innodb, Falcon Benchmarks

…= 5 LIMIT 1206,18\G *************************** 1. row *************************** id:…index structure for such data distribution but good enough for performance gotcha illustration purposes. The benchmark shows following results for MyISAM… single index had most of the …30.3364 no-vmlinux (no symbols)…

Post: To SQL_CALC_FOUND_ROWS or not to SQL_CALC_FOUND_ROWS?

… set, another – to count total number of rows. In this post I’ll try…KEY (`a`), KEY `bc` (`b`,`c`) ) ENGINE=MyISAM Test data has been created with… would take: mysql> SELECT SQL_NO_CACHE count(*) FROM count_test WHERE b… first 5 rows specified in LIMIT clause). With count(*) it used index scan inly …

Post: MySQL EXPLAIN limits and errors.

of row combinations really examined. LIMIT is not taken into account while estimating number of rows Even if you have LIMIT which restricts how many rowsof table in memory may be done at speed of millions of rows per second, while retrieval of large rows from uncached table by random index

Post: To pack or not to pack - MyISAM Key compression

… packed indexes not a bit longer rows is frequent reason of MyISAM…c` (`c`), KEY `id` (`id`) ) ENGINE=MyISAM Index size: PACK_KEYS=DEFAULT – …limit 1 – forward index scan select c from t1 where c like “%abc%” order by c desc limit 1 – reverse indexindexes in memory by packing them it is almost no

Post: Redundant index is not always bad

… (`state_id`), ) ENGINE=MyISAM with 1,000,000 rows, and…index, which store all needed columns in the index, and there is no need to read rowlimited available memory to fit only one index, that shows how can degrade performance if we balance on memory limits…08 q/s And INSERT of 1mil records: only with…

Post: Dynamic row format for MEMORY tables

Indexes on BLOB columns are not supported. While we do not consider these limitationsof rows inserted). In the second test we check if the dynamic rowMyISAM tables are still used for temporary tables where the MEMORY tables with dynamic row

Post: InnoDB Full-text Search in MySQL 5.6: Part 2, The Queries!

MyISAM full-text parser code, convert it to a plugin, and use it for InnoDB FT indexes where you’re expecting MyISAM