Network
Join Attendee Network
 

Making MySQL Better for the Data Center

Mark Callaghan (Facebook), Ryan Mack (Facebook), Vamsi Ponnekanti (Facebook)
2:50pm Thursday, 04/14/2011
Replication and Scale-Out, Storage Engine Development and Optimization
 Location: Ballroom B
Tags: mysql, data_centers, case_study, facebook
Average rating: ****.
(4.33, 3 ratings)

The Facebook database engineering team works with the community and on its own to make MySQL better for data center deployments. This work is visible in the Facebook patch, bugs fixed in official MySQL and features sponsored in other distributions. We will describe work completed, in progress and planned to support a large number of large databases. We focus on backup, replication and quality of service.

We intend to put more data on our servers while improving quality of service. To achieve this goal we must improve backup and replication. We must also remove sources of downtime and intermittent stalls in MySQL.
  • replication – single-threaded slaves are not able to keep up with a busy master on IO-bound loads
  • backup – incremental hot backup is the future
  • downtime – master failover and schema changes are operations that typically cause downtime
  • stalls – there are a few sources of intermittent stalls in InnoDB. Most of these are much worse on IO-bound loads.

We write about our work at MySQLatFacebook.

Photo of Mark Callaghan

Mark Callaghan

Facebook

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.

Photo of Ryan Mack

Ryan Mack

Facebook

Ryan is a member of the database engineering team at Facebook where he works on improving scalability and performance. He was formerly a video game AI and performance engineer at Rockstar San Diego and Sony Computer Entertainment San Diego Studio.

Vamsi Ponnekanti

Facebook

Vamsi is a member of the database engineering team at Facebook. He implemented the online schema change tool (OSC) and is currently working on improvements for incremental hot backup.

  • EnterpriseDB
  • Amazon Web Services
  • Clustrix
  • Continuent
  • Facebook
  • HTI Consultoria e Tecnologia
  • Monty Program
  • Percona
  • Rackspace Hosting
  • Schooner Information Technology
  • SkySQL
  • Xeround

Sponsorship Opportunities

For information on exhibition and sponsorship opportunities at the conference, contact Yvonne Romaine at yromaine@oreilly.com

Media Partners Opportunities

For media partnerships, contact mediapartners@ oreilly.com

Press & Media

For media-related inquiries, contact Maureen Jennings at maureen@oreilly.com

O'Reilly MySQL Conference Bulletin

To stay abreast of conference news and to receive email notification when registration opens, please sign up for the O'Reilly MySQL Conference Bulletin (login required).

Contact Us

View a complete list of O'Reilly MySQL Conference Contacts