Aurora MySQL scaling with query router

1. Aurora DB cluster
Scaling/Load balancing
By Sudheer Kondla
skondla@me.com
Senior Data Platform Architect

2. Agenda
´ Review transactions - read/writes %.
´ Under utilized Aurora Cluster (idle replicas)
´ Off-loading reads to replicas to scale out Aurora Cluster
when demand increases. (up to 15 replicas)
´ Cannot scale up the writer. We are already using the
largest Aurora instance.
´ Application connection pool settings, data source
configurations
´ ScaleArc for Query routing.

3. Current Setup in EU-WEST-1
´

4. Database Load Balancer/Query Router

5. Database Load Balancer/Query Router - HA

6. Query Router/DB Load Balancer - ScaleArc
´ Leading provider of database load balancing software.
´ ScaleArc software inserts transparently between
applications and databases,
´ Creates an agile data tier that provides continuous
availability and increased performance for all apps.
´ ScaleArc, enterprises also gain instant database scalability
and a new level of real-time visibility for their application
environments, both on premise and in the cloud.
´ ScaleArc supports MySQL and Microsoft SQL Server
databases.
´ Compatible with Aurora

7. DB Load balancing with ScaleArc
´ Benefits of ScaleArc
´ Automated failover HA
´ ScaleArc shields applications from downtime and errors because it
´ Operates at the SQL protocol layer and instantly and
transparently routes database traffic around downed servers
´ Transverses multiple data centers or AZs for maximum
availability-ensuring business continuity for SQL environments.
´ Zero downtime maintenance
´ ScaleArc optimizes traffic flow by:
´ Applying software/security updates,
including schema change
´ Performing storage maintenance
´ Implementing principal/slave failover
´ Diagnosing potential performance issues
´ Cloud migration
´ Improved app availability
´ Database scalability

8. DB Load balancing with ScaleArc
´ ScaleArc features
´ Automated Failover
´ Connection pooling and multi-plexing
´ Surge Queue
´ Query caching
´ Centralized logging
´ Read/Write split
´ Dynamic load balancing
´ Query firewall
´ https://doc.scalearc.com/mysql311/scalearc-guide-for-mysql/introducing-
scalearc/scalearc-features

9. Tune DB
´ Review DB parameters and adjust one at a time if needed
´ Basic Settings:
´ innodb_buffer_pool_size
´ innodb_log_file_size
´ max_connections
´ InnoDB Settings
´ innodb_file_per_table
´ innodb_flush_log_at_trx_commit
´ innodb_flush_method
´ innodb_log_buffer_size
´ Other Settings
´ query_cache_size
´ log_bin
´ skip_name_resolve

10. Tune SQL
´ Optimizing SELECT Statements
´ Where clause Optimization
´ Range Optimization
´ Index Merge Optimization
´ Engine Condition Pushdown Optimization
´ Nested-Loop Join Algorithms
´ Nested Join Optimization
´ Left Join and Right Join Optimization
´ Outer Join Simplification
´ IS NULL Optimization
´ ORDER BY Optimization
´ GROUP BY Optimization
´ DISTINCT Optimization
´ LIMIT Query Optimization
´ Function Call Optimization
´ Row Constructor Expression Optimization
´ Avoid Full Table Scans
´ https://dev.mysql.com/doc/refman/5.5/en/select-optimization.html

11. Additional Performance Considerations
´ Slow Query Log
´ Max Connections
´ Worker Threads
´ Key Buffer
´ Query Cache
´ Sort Buffer
´ JoinsTemp
´ TablesTable (Open & Definition) Cache
´ Table Locking
´ Table Scans (read_buffer)
´ Innodb Status

12. Q & A
´Thank You
´skondla@me.com