… pretty nice article about MyISAM features so I thought I would share my own view on using MyISAM in production. For me it is not only about table locks. Table locks is only one of MyISAM limitations you need to consider using it in production. Especially if you’re comming from…
Post: ANALYZE: MyISAM vs Innodb
September 3, 2008 By 9 Comments
… TABLE for MyISAM and Innodb. But before we go into that I wanted to highlight about using ANALYZE TABLE in production as… equal when computing stats: mysql> show variables like “myisam_stats_method”; +———————+—————+ | Variable_name | Value | +———————+—————+ | myisam_stats_method | nulls_unequal | +———————+—————+ 1 row in…
Post: MyISAM Scalability and Innodb, Falcon Benchmarks
October 12, 2007 By 10 Comments
… for MyISAM tables. We saw that several times in synthetic benchmarks but never in production, that’s why we did not escalate MyISAM…) unsigned NOT NULL, PRIMARY KEY (`id`), KEY `val` (`val`) ) ENGINE=MyISAM AUTO_INCREMENT=4097 Table t1 contains about 260,000 records… performance gotcha illustration purposes. The benchmark shows following results for MyISAM using MySQL 5.0.45 run on 4 Core System…
Post: Crashes while using MyISAM with multiple key caches
July 18, 2009 By Leave a Comment
… of years I have ran into random MySQL crashes in production when multiple key caches were used. Unfortunately this never was… is very rare one would resize single key cache in production and it only triggers crash sometimes, while if you’re… in MySQL 5.0 after MySQL 5.1 is in production for a few months but I trust this was forgotten…
Comment: Innodb Performance Optimization Basics
January 12, 2009 By 70 Comments
[...] can be as much as 10-50 times for Innodb tables in particular for write intensive workloads. Check here for details. Posted by peter @ 1:49 pm :: Innodb, myisam, production Print This Post [...]
Post: Beware of running ANALYZE in Production
September 2, 2008 By 10 Comments
… just quickly updates table statistics using index dives, unlike with MyISAM when it scans indexes holding table lock for long period…
Post: Finding your MySQL High-Availability solution – The questions
October 16, 2009 By 36 Comments
… with MMM manager” Don’t use any special MyISAM feature All Can change MyISAM Full text to Sphinx All 4. What is… is a full production setup that includes extensive testing, fire drills, full documentation, monitoring, alerting, backups, migration to production and post migration… for the most complex solutions. Proof of concept Migration to Production MySQL replication 4 hours 12 hours Master-Master with MMM…
Post: How fast is FLUSH TABLES WITH READ LOCK?
April 24, 2010 By 28 Comments
… with them about their MySQL backup product. One of the representatives told me that their backup product uses FLUSH TABLES WITH READ… operation. Conclusion A backup system that is designed for real production usage must not assume that FLUSH TABLES WITH READ LOCK…, it is unavoidable. This includes backing up a mixture of MyISAM and InnoDB data. But many installations do not mix their…
Comment: Air traffic queries in MyISAM and Tokutek (TokuDB)
November 6, 2009 By 26 Comments
… MyISAM. 2) Given that the indexes were built with a single bulk load, the MyISAM indexes are not fragmented. That makes the MyISAM… month at a time, then the MyISAM insertions would not do so well, and the MyISAM indexes would be fragmented, and would… best case, B-trees are pretty good. Whereas in in production, many databases are performing close to worst-case insertion workloads…
Comment: Unused indexes by single query
September 14, 2008 By 14 Comments
… indexes. In our book we have benchmark for InnoDB and MyISAM: To insert 1 million records in InnoDB with 1 index took 80 sec, with 2 indexes – 136 seconds. For MyISAM the difference is bigger: 72 sec vs 470 sec. And… for usage in production – it is surely each own decision. We use it in production, Google uses it in production, we ported this…
