June 19, 2013

Post: InnoDB vs MyISAM vs Falcon benchmarks - part 1

… KB 16GB of RAM MySQL version We used MySQL 5.1.14-beta sources for MyISAM / InnoDB and MySQL 5.1.14-falcon… lot in next releases) Compilation parameters: For MyISAM / InnoDB ./configure –prefix=/usr/local/mysqltest/mysql- –with-innodb For Falcon ./configure –prefix=/usr/local…=128 MyISAM / InnoDB: libexec/mysqld –no-defaults –user=root –key-buffer-size=1500M –innodb-buffer-pool-size=1500M –innodb-log-file-size=100M –innodb-thread…

Post: Recovering Innodb table Corruption

… in MyISAM table so all you have to do is to drop old table and convert new table back to Innodb after… you simply rebuild table by using OPTIMIZE TABLE ? This is because Running in innodb_force_recovery mode Innodb becomes read only for data… not work well – in this case you may wish to use Innodb Recovery Toolkit which is also helpful in cases you’ve…

Post: MyISAM Scalability and Innodb, Falcon Benchmarks

… performance gotcha illustration purposes. The benchmark shows following results for MyISAM using MySQL 5.0.45 run on 4 Core System: Threads… when single query executed being 1/3rd of MyISAM and 1/6th of Innodb. On other hand it scales quite nicely as…. Here is comparison of MyISAM Innodb and Falcon results in the graphical form: I’ve created bug, for MyISAM key cache contention issue…

Post: Innodb Table Locks

Innodb uses row level locks right ? So if you see locked tables reported in SHOW ENGINE INNODB STATUS you might be confused and rightfully so as Innodb table locking is a bit more complicated than traditional MyISAM table… you may spotted important difference between MyISAM and Innodb when it comes to Table Level Locks. For MyISAM tables running UPDATE query on…

Post: How innodb_open_files affects performance

… variable – innodb_open_files which defines how many files Innodb will keep open while working in innodb_file_per_table mode. Unlike MyISAM Innodb does… create Innodb tables you better store some data in them otherwise there will be a huge waste of space. I used MySQL… even in case table it fully in Innodb data dictionary the operation is slower than MyISAM tables. Though the difference can be…

Post: My Innodb Feature wishes

… difference in Performace with MyISAM and Innodb is huge for read only workload it is caused by the fact Innodb does not have prefix compression for its indexes, as MyISAM has which in certain cases… times space compression. Insert buffer for delete. For Insert operation Innodb uses nice tecnique called Insert Buffer which speeds up inserts for…

Post: The perils of InnoDB with Debian and startup scripts

… on a server with MyISAM tables, if there are enough tables, but it is far worse on InnoDB. There are a few…-grade RAID storage. Since they have a lot of tables, InnoDB uses over 3.5G of memory for its data dictionary (the… id 1159956816 starting index read, thread declared inside InnoDB 500 mysql tables in use 7, locked 0 MySQL thread id 6424, query…

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

…: CREATE TABLE `innodb_myisam_stopword` ( `value` varchar(18) NOT NULL DEFAULT ” ) ENGINE=InnoDB DEFAULT CHARSET=utf8 But, when we try to use this table, here’s what comes back: mysql: SET GLOBAL innodb_ft_server_stopword_table=’test/innodb_myisam_stopword’; ERROR 1231 (42000): Variable ‘innodb

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

… advantages to using MyISAM are far outweighed by the potential disadvantages and the strengths of InnoDB. However, up until MySQL 5.6, MyISAM was… the prudent move would be a migration to InnoDB, but due to their use of MyISAM FTS, the idea of a complete or… the MyISAM default. After all, the (naive?) hope here is that when I run an FTS query against both MyISAM and InnoDB I…

Post: ANALYZE: MyISAM vs Innodb

… by ANALYZE TABLE for MyISAM and Innodb. But before we go into that I wanted to highlight about using ANALYZE TABLE in production… in the difference of behavior of ANALYZE TABLE for MyISAM vs Innodb. I used the following simple table for tests: CREATE TABLE `antest… significantly. This means Innodb and MyISAM have different stats computation method by default. Lets check how stats change for MyISAM if we change…