We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Optimizing MySQL without SQL or touching my.cnf

Formal Metadata

Title
Optimizing MySQL without SQL or touching my.cnf
Title of Series
Number of Parts
611
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language
Production Year2017

Content Metadata

Subject Area
Genre
Abstract
At Dropbox, with 1000s of machines running MySQL, performance is important.Among other things, out team is responsible for our MySQL servers being tunedwell. In this talk, we will talk about the performance impact of“environmental” MySQL tuning, where the tuning is neither at the SQL level(like creating indexes or using different table structures), nor with settingMySQL parameters (tuning parameters like innodb _buffer_ pool _size or innodb_log _file_ size even more obscure ones like innodb _lru_ scan_depth). Instead,in the talk we will cover the following areas (we won’t limit the talk tothese): * Operating system level tuning opportunities * Compiling MySQL: does it worth to build your own from the performance perspective? * Building MySQL with different compilers * Building MySQL with profile-guided optimization * Impact of using different memory allocators * CPU and memory affinity with running multiple instances The experiments we conducted here helped us to make more educated decisionsabout how to run MySQL at Dropbox.