What happens after you launch a product that depends on MySQL and the product becomes successful? Suddenly everyone expects much more from the MySQL deployment and everyone includes database users, bosses, auditors and the general public. I will describe the work we have done to meet these expectations from 2006 until today. The work continues as problems change, new problems arrive and our understanding of the system improves.
Mark lead the MySQL Engineering team at Google for 2.5 years and continues to focus on making MySQL perfect. The team supports a large and critical MySQL deployment. During this time the team has implemented, deployed and published many valuable features for MySQL including 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 maintains MySQL patches at code.google.com and launchpad.net and writes a popular blog at mysqlha.blogspot.com.
Add a comment (requires login)
For information on exhibition and sponsorship opportunities at the conference, contact Sharon Cordesse at scordesse@oreilly.com
Download the MySQL Sponsor/Exhibitor Prospectus
Download the Media & Promotional Partner Brochure (PDF) for information on trade opportunities with O'Reilly conferences or contact mediapartners@ oreilly.com
For media-related inquiries, contact Maureen Jennings at maureen@oreilly.com
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the MySQL Conference newsletter.
View a complete list of MySQL contacts.
Comments
for a typical vauge Google presentation it was pretty good. Not what I would think of a keynote though.