InnoDB

• InnoDB has been designed for maximum performance when processing large data volumes.
  • InnoDB is used in production at numerous large database sites requiring high performance.

• InnoDB provides MySQL with a transaction-safe storage engine that has commit, rollback, and crash recovery capabilities.

• InnoDB does locking on the row level and also provides an Oracle-style consistent non-locking read in SELECT statements.
  • This increases multi-user concurrency and performance.

• There is no need for lock escalation in InnoDB because row-level locks fit in very little space.

• InnoDB also supports FOREIGN KEY constraints.

• One can freely mix InnoDB tables with tables from other MySQL storage engines, even within the same statement.

• Fully integrated with MySQL Server, the InnoDB storage engine maintains its own buffer pool for caching data and indexes in main memory.
  • InnoDB stores its tables and indexes in a tablespace, which may consist of several files (or raw disk partitions).
  • This is different from MyISAM tables where each table is stored using separate files.

• InnoDB tables can be of any size even on operating systems where file size is limited to 2GB.

• InnoDB is included in binary distributions by default.

How do I configure InnoDB?

---

---

© 2007 John Michael Pierobon

Notes