MySQL: Innodb or MyISAM? What's your preference? - The Diigo Meta page

• 27 Jan 12
  

  mohammed shannaq

  using MyISAM or Innodb

  mysql innodb myisam database

• 13 May 11
  

  S d

  mysql isam_vs_innodb

  • there are many modifications of the data, it's said that InnoDB works faster because it uses row locking instead of table locking, like MyISAM. However, if there are mainly SELECT statements, a MyISAM table might be faster.
    
    However, it's always important what the needs of a specific table are - so I would choose the storage engine that best fits the requirements for the given table. If you need foreign key constraints or transactions, you can only use InnoDB, wheras if you need fulltext indexes, you can only use MyISAM tables at the moment.
    
    With replication it's even possible to take advantage of both storage engines on one table. For example, the master could store a table as InnoDB which makes it fast for INSERTs, UPDATEs and DELETEs while the slave(s) could store the same table as MyISAM and offer the best performance for SELECTs.
• 26 Feb 09
  

  Alex Butcher

  innodb myisam mysql

• 27 Nov 08
  

  Kenyth Zeng

  discussion mysql Storage Engine comparison performance database blog starred

  • or do you try to find a balance between both by having tables of both kinds?
  • If there are many modifications of the data, it's said that InnoDB works faster because it uses row locking instead of table locking, like MyISAM.
  • If you need foreign key constraints or transactions, you can only use InnoDB, wheras if you need fulltext indexes, you can only use MyISAM tables at the moment.
  • With replication it's even possible to take advantage of both storage engines on one table.
  • Unfortunately there's a little uncertainty about the long-term future of InnoDB inside MySQL since Oracle bought Innobase and with it the InnoDB storage engine.
  • innoDB for fast inserting, and the other is MyISAM for fulltext searching.
  • InnoDB for most of the tables, including the messaging
  • MyISAM (packed, preferably) for static data
  • For reliability and performance, we use InnoDB for almost everything at Wikipedia - we just can't afford the downtime implied by MyISAM use and check table for 400GB of data when we get a crash.
  • At Wikipedia we achieved some major performance gains by exploiting the way InnoDB clusters records by their primary key.
  • We used to use MyISAM for fulltext, duplicating the data in the InnoDB master table.
  • We abandoned it and switched to Lucene.

  10 more annotations...

• 10 Nov 07
  

  Sokratis Galiatsis

  mysql innodb myisam database performance design tips delicious

• 15 Dec 06
  

  MySQL: Innodb or MyISAM? What's your preference?

  mysql sql bdd optimisation engine index formats innodb myisam database

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.