Movatterモバイル変換

EnablingInnoDB to use high-performance memory allocators on systems that include them. SeeSection 14.8.4, “Configuring the Memory Allocator for InnoDB”.

Controlling the types of data change operations for whichInnoDB buffers the changed data, to avoid frequent small disk writes. SeeConfiguring Change Buffering. Because the default is to buffer all types of data change operations, only change this setting if you need to reduce the amount of buffering.

Turning the adaptive hash indexing feature on and off using theinnodb_adaptive_hash_index option. SeeSection 14.5.3, “Adaptive Hash Index” for more information. You might change this setting during periods of unusual activity, then restore it to its original setting.

Setting a limit on the number of concurrent threads thatInnoDB processes, if context switching is a bottleneck. SeeSection 14.8.5, “Configuring Thread Concurrency for InnoDB”.

Controlling the amount of prefetching thatInnoDB does with its read-ahead operations. When the system has unused I/O capacity, more read-ahead can improve the performance of queries. Too much read-ahead can cause periodic drops in performance on a heavily loaded system. SeeSection 14.8.3.4, “Configuring InnoDB Buffer Pool Prefetching (Read-Ahead)”.

Increasing the number of background threads for read or write operations, if you have a high-end I/O subsystem that is not fully utilized by the default values. SeeSection 14.8.6, “Configuring the Number of Background InnoDB I/O Threads”.

Controlling how much I/OInnoDB performs in the background. SeeSection 14.8.8, “Configuring InnoDB I/O Capacity”. You might scale back this setting if you observe periodic drops in performance.

Controlling the algorithm that determines whenInnoDB performs certain types of background writes. SeeSection 14.8.3.5, “Configuring Buffer Pool Flushing”. The algorithm works for some types of workloads but not others, so might turn off this setting if you observe periodic drops in performance.

Taking advantage of multicore processors and their cache memory configuration, to minimize delays in context switching. SeeSection 14.8.9, “Configuring Spin Lock Polling”.

Preventing one-time operations such as table scans from interfering with the frequently accessed data stored in theInnoDB buffer cache. SeeSection 14.8.3.3, “Making the Buffer Pool Scan Resistant”.

Adjusting log files to a size that makes sense for reliability and crash recovery.InnoDB log files have often been kept small to avoid long startup times after a crash. Optimizations introduced in MySQL 5.5 speed up certain steps of the crashrecovery process. In particular, scanning theredo log and applying the redo log are faster due to improved algorithms for memory management. If you have kept your log files artificially small to avoid long startup times, you can now consider increasing log file size to reduce the I/O that occurs due recycling of redo log records.

Configuring the size and number of instances for theInnoDB buffer pool, especially important for systems with multi-gigabyte buffer pools. SeeSection 14.8.3.2, “Configuring Multiple Buffer Pool Instances”.

Increasing the maximum number of concurrent transactions, which dramatically improves scalability for the busiest databases. SeeSection 14.6.7, “Undo Logs”.

Moving purge operations (a type of garbage collection) into a background thread. SeeSection 14.8.10, “Purge Configuration”. To effectively measure the results of this setting, tune the other I/O-related and thread-related configuration settings first.

Reducing the amount of switching thatInnoDB does between concurrent threads, so that SQL operations on a busy server do not queue up and form a“traffic jam”. Set a value for theinnodb_thread_concurrency option, up to approximately 32 for a high-powered modern system. Increase the value for theinnodb_concurrency_tickets option, typically to 5000 or so. This combination of options sets a cap on the number of threads thatInnoDB processes at any one time, and allows each thread to do substantial work before being swapped out, so that the number of waiting threads stays low and operations can complete without excessive context switching.