How we sped up MySQL Handler Socket ninefold
summary
The talk describes using MySQL HandlerSocket as a non-SQL data-access interface for the high-load Wamba.ru project because the standard SQL interface could not handle the traffic. It explains that as load grew HandlerSocket also started to fail and outlines the work done to speed up HandlerSocket performance by about 9× to avoid constant provisioning of more MySQL replicas.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 3:42Tarantool introduction
- 5:27MySQL 5.7 replicator adaptation
- 9:48HandlerSocket vs Tarantool performance
- 11:35Why Tarantool is faster
- 12:37Replicating only needed data
- 15:06Tarantool deployment results
- 16:56Post-failure recovery
- 17:40Tarantool community and support
- 19:50Data consistency checks
- 21:16Tarantool drawbacks
- 22:20Replicator license and development
- 23:47Summary and resource savings
- 24:11Q&A: Replicator crash
- 26:19Q&A: App rewrite
- 27:43Q&A: Hardware issues
- 29:54Q&A: Checksums and IronDB
- 30:58Q&A: MariaDB support
- 31:39Q&A: Alternative solutions
- 32:25Q&A: System architecture
- 35:05Q&A: Server resources
- 36:53Q&A: ALTERs and data structure
related talks
16mHow to improve MySQL performance even with Handler Socket with replication to in-memory Tarantool
49mHighLoad Solutions On MySQL
49mHighLoad Solutions On MySQL
30mFrom 15,000 Database Connections to under 100—A Tech Debt Tale
49mHighLoad Solutions On MySQL
48mMySQL Load Balancers - MaxScale, ProxySQL, HAProxy, MySQL Router & nginx - a close up look
55mProxySQL Use Case Scenarios
37mScale MySQL beyond limits with ProxySQL
