High Quality
Open the downloaded document, and select print from the file menu (PDF reader required).
Linux and H/W optimizationsfor MySQL
Yoshinori Matsunobu
Principal Infrastructure Architect, DeNA FormerAPAC Lead MySQLConsultant at MySQL/Sun/OracleYoshinori.Matsunobu@dena.jp
Table of contents
MySQLperformance overview and improvement history
SSD and MySQLperformance
Memory and swap space management
File I/O
Network
Useful command line toolsand tips
History of MySQLperformance improvements
H/W improvements
HDD RAID, Write Cache
Large RAM
SATA SSD
、
PCI-Express SSD
More number of CPU cores
Faster Network
S/W improvements
Improved algorithm (i/o scheduling, swap control, etc)
Much better concurrency
Avoiding stalls
Improved space efficiency (compression, etc)
Linux and H/W optimizations for MySQL
Info and Rating
Sections
« prev | next »- Table of contents
- 32bit Linux
- 64bit Linux + large RAM + BBWC
- Avoiding sudden performance drops
- Avoiding stalls
- Avoiding stalls(2)
- Handling Real-World workloads
- RDBMS or NoSQL?
- Social Game workloads
- INSERT-mostly tables
- InnoDBFeature: Insert Buffering
- INSERT gets slower
- INSERT performance difference
- UPDATE-mostly tables
- What do you need to consider?
- Why SSD? IOPS!
- Random Read benchmark
- High Concurrency
- PCI-Express SSD
- Write performance on SSD
- Reserved Space
- Write performance deterioration
- Sequential I/O
- fsync() speed
- HDD is fast for sequential writes / fsync
- Filesystemmatters
- Changing I/O unit size
- Changing I/O unit size on FusionIO
- SLC vsMLC(16KB)
- SLC vsMLC (8KB)
- tachIOnvsFusionIO(SLC)
- PCI-Express interface and CPU util
- # of interfaces (tachIOnSLC)
- # of interfaces (FusionIOMLC)
- How about using SSD as L2 Cache?
- Virtualization?
- Virtualization benchmarks (HDD)
- HDD vsIntel SSD vsFusion I/O
- MySQLfile location
- Does CPU matter?
- Enable HyperThreading
- MySQL5.5
- Our environment
- Statistics
- CPU loads
- Things to consider
- taskset
- Application Design
- Making MySQLbetter
- Conclusion for choosing H/W
- Conclusion for database deployments
- Random Access Memory
- Cache hot application data in memory
- Use Direct I/O
- Do not allocate too much memory
- What if setting swap size to zero?
- Do not set swap=zero
- What if stopping OOM Killer?
- Swap space management
- Be careful about backup operations
- vm.swappiness= 0
- Swap caused by log files
- Tool: unmap_mysql_logs
- Performance effect
- Memory allocator
- File I/O and synchronous writes
- BBWC and “Auto Learn”Issues
- FBWC
- Overwriting or Appending?
- Quick file i/o health check
- Buffered and asynchronous writes
- Filesystem–ext3
- Tip: fast large file remove
- Filesystem–xfs/ext2
- Concurrentwrite matters on fast storage
- I/O scheduler
- cfqmadness
- Fighting against network bottlenecks
- Tx/Rx multiqueue
- Be careful about bandwidth
- Remote datacenter
- Waiting three seconds for SYN
- Database connections
- Persistent Connections
- Use persistent connections properly
- Proxy-based connection pooling
- Thread pooling within MySQL
- Useful commands and tools
- iostat
- iostatexample(DBT-2)
- mpstat
- Typical mpstatoutput
- dstat
- Oprofile
- Oprofileexample
- Checking stalls
- Checking stalls by gdbor pmp
- gdbcase study
- Taking thread dumps with gdb
- Stack Trace
- Reading sql_parse.cc:969
- Reading mysqld.cc:4811
- Poor Man’s Profiler
- pmpoutput example
- Disadvantages of gdb/pmp
- gcore
- Case study
- From mysqlstatus
- Core file analysis example
- Dumping slave’s tmptables info
- Capturing MySQLpackets
- tcpdump+ mk-query-digest
- MySlowTranCapture
- SSD
- RAM
- File I/O
- CPU, Network, Virtualization
Add a Comment