My Sql Performance In A Cloud

2,239 views
2,142 views

Published on

Mark Callaghan's Talk on MySQL User Conference 2009.

Published in: Technology
0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,239
On SlideShare
0
From Embeds
0
Number of Embeds
13
Actions
Shares
0
Downloads
100
Comments
0
Likes
5
Embeds 0
No embeds

No notes for slide

My Sql Performance In A Cloud

  1. 1. MySQL cloud performance Mark Callaghan
  2. 2. Special thanks Eric Hammond (http://www.anvilon.com) provided documentation that made all of my work much easier.
  3. 3. What is this thing called a cloud? Deployment trends Technology Public versus private
  4. 4. Deploying MySQL in a cloud New problems New benefits Differences from traditional deployment Performance can be good, but ... Virtualization techniques matter May need InnoDB patches to tolerate IO latency
  5. 5. Impact from requirements Database in direct attached storage: backups and binlogs archived in the cloud use MySQL replication to maintain a failover target less can go wrong   Database in network attached storage another MySQL server can takeover on failure
  6. 6. Focus on InnoDB performance Network attached storage Direct attached storage Multi-core servers Virtualization overhead Patches that improve performance
  7. 7. Benchmarks Start with simple benchmarks iibench IO bound workload great for finding bottlenecks in storage engines started by Tokutek sysbench OLTP workload wisconsin query processing workload
  8. 8. What is different? Not much, MySQL runs great here Multi-core scalability matters because 8-cores costs more May need ability to tolerate IO latency
  9. 9. Make InnoDB faster link with tcmalloc use XFS reduce mutex contention for multi-core servers IO performance multiple background IO threads increase IO rate on busy servers
  10. 10. Factors for IO latency O_DIRECT versus buffered IO SATA writeback cache Flash erase cycles Network versus direct attached storage IO scheduler Excessive prefetching from the OS Hardware RAID write cache File system limits on concurrent reads/writes per file Ability of storage engine to issue concurrent IO requests
  11. 11. Tuning for IO bound loads innodb_read_io_threads In Percona and Google patches Helps when there is a lot of prefetching for full table scans   innodb_write_io_threads In Percona and Google patches Helps when writes have a lot of latency Writes have a lot of latency when: using O_DIRECT without SATA writeback cache using O_DIRECT without HW RAID write cache using network attached storage
  12. 12. Tuning for IO bound loads (2) innodb_io_capacity In Google and Percona patches Helps when there are many writes to issue   faster IO Increases rate at which background IO is done Increase size of IO request arrays Google and Percona patches have changes for this   SHOW INNODB STATUS Google and Percona added more output Google patch includes average IO time for reads and
  13. 13. Network attached storage tests Server: 2 CPU cores, 4G or 8G RAM SW RAID 0 striped over 4 network volumes 1M RAID stripe size XFS MySQL 5.0.37 + v3 Google patch + tcmalloc Innodb with 1G buffer pool, O_DIRECT, innodb_flush_log_at_trx_commit=2
  14. 14. Concurrent query performance with network attached storage: 4 concurrent queries, IO bound
  15. 15. iibench insert rate
  16. 16. iibench QPS rate from 4 threads concurrent with inserts
  17. 17. Direct attached storage tests Server: 2 CPU cores, 4G or 8G RAM SW RAID 0 striped over 2 disks 1M RAID stripe size XFS Innodb with 1G buffer pool, O_DIRECT, innodb_flush_log_at_trx_commit=2 MySQL 5.0.37 + v3 Google patch + tcmalloc
  18. 18. Concurrent query performance with direct attached storage: 2 concurrent queries, IO bound
  19. 19. iibench insert rate
  20. 20. Direct attached storage tests (2) Server: 8 CPU cores, 4G or 8G RAM SW RAID 0 striped over 10 disks 1M RAID stripe size ext-2 Innodb with 1G buffer pool, O_DIRECT, innodb_flush_log_at_trx_commit=2 MySQL 5.0.37 + v3 Google patch + tcmalloc  
  21. 21. Time to load 50M rows in iibench
  22. 22. Row insert rate while loading 50M rows in iibench
  23. 23. Multi-core servers How do MySQL and InnoDB scale on SMP? Test configuration: CPU bound workload MySQL 5.0.37 with v3 Google patch 4, 8 and 16 core servers mysqld linked with tcmalloc
  24. 24. CPU speedup without virtualization: modified sysbench readonly, CPU bound measure transactions per second
  25. 25. CPU speedup without virtualization: modified sysbench readwrite, CPU bound measure transactions per second
  26. 26. Virtualization overhead KVM tests Ubuntu 8.04 4 core server, 1 disk, 4G RAM, supports AMD-V MySQL 5.0.77 with tcmalloc MySQL 5.0.37 with v3 Google patch and tcmalloc Note that KVM is much improved since this version   Xen tests Linux 2.6 8 CPU cores, enough RAM to cache database hardware on server with Xen faster than non-Xen server Xen server has 4 disks in SW-RAID 0 using XFS, 16G
  27. 27. KVM random IO performance: sysbench fileio rndrd, 8G file
  28. 28. Xen random IO performance: sysbench fileio rndrd, 16G file
  29. 29. KVM sequential IO performance: sysbench fileio seqrd, 8G file
  30. 30. Xen sequential IO performance: sysbench fileio seqrd, 16G file
  31. 31. KVM sequential IO performance: hdparm  -t, hdparm -T
  32. 32. KVM CPU performance: modified wisconsin benchmark, CPU bound measure time to run all queries
  33. 33. KVM CPU performance: modified sysbench readonly, CPU bound measure transactions per second
  34. 34. KVM CPU performance: modified sysbench readwrite, CPU bound measure transactions per second
  35. 35. Xen CPU performance: modified sysbench OLTP readonly, CPU bound
  36. 36. Xen CPU performance: modified sysbench OLTP readwrite, CPU bound
  37. 37. iibench insert rate comparing 2 local disks versus 4 network volumes
  38. 38. iibench QPS rate comparing 2 local disks versus 4 network volumes
  39. 39. Patches All of these changes are available in some combination of the v3 Google patch, Percona builds and now .... MySQL 5.4!
  40. 40. Make appropriate choices remote versus direct attached storage configuration storage engine IO scheduler file system patches

×