The InnoDB storage engine is an amazing work of engineering and art. But it has a flaw. It was designed for servers with few CPU cores and few disks. Design decisions made then limit the scalability of InnoDB on today’s commodity servers, which happen to have many disks and CPU cores. InnoDB and the MySQL community are working hard on fixing these problems. I will describe the performance problems in the official release and fixes for the problems that have been developed by InnoDB, Google and the MySQL community.
Mark leads the MySQL engineering team at Facebook. The team makes MySQL better for a large and critical deployment. The team writes about their work at MySQLatFacebook and publishes patches for MySQL at launchpad.
He previously lead the MySQL engineering team at Google. The team published a popular patch for MySQL that included semi-sync replication, user and table monitoring via SHOW TABLE_STATISTICS and USER_STATISTICS, SMP and IO performance patches for InnoDB, global transaction IDs for replication, row-change logging, transactional replication and many bug fixes.
Prior to Google Mark worked at Identity Engines, Oracle and Informix on database internals. Mark holds an M.S. degree in Computer Science from the University of Wisconsin-Madison. He occasionally writes about MySQL at mysqlha.blogspot.com.
View a complete list of MySQL contacts.