Solving our replication bottleneck

Trends in Architecture and Design
24 April 4:30pm - 5:20pm @ Ballroom F

At SugarSync we selected MySQL due to it's popularity and it originally met our needs. As our customers grew, we have had to investigate and use other tools to allow us to scale MySQL.

In this talk, we'll describe how we solved our replication bottleneck in MySQL Version 5.1 (Percona-Server-server-51-5.1) by installing Continuent Tungsten. This included:
• Using parallel replication because MySQL native replication could not handle our work load
• Consolidating a central database from 3 database schemas into one MySQL instance
• Splitting our shards
• Using many small schemas per server
• Reevaluating our hardware for our new requirements
• Compression


Brandon Bercovich
Lead Systems Administrator, SugarSync
Brandon has been working as a Systems Administrator for over 12 years. For the last four years he has been working at SugarSync improving their sharded database infrastructure and finding ways to increase capacity.