The purge operations (a type of garbage collection) that InnoDB performs automatically may be performed by one or more separate threads rather than as part of the master thread. The use of separate threads improves scalability by allowing the main database operations to run independently from maintenance work happening in the background.
InnoDB自動執行的purge 操作(一種垃圾收集類型)可以由一個或多個單獨的線程執行，而不是作爲master thread的一部分。使用單獨的線程可以通過允許主數據庫操作獨立於後臺執行的維護工作來提高可伸縮性。
To control this feature, increase the value of the configuration option innodb_purge_threads. If DML action is concentrated on a single table or a few tables, keep the setting low so that the threads do not contend with each other for access to the busy tables. If DML operations are spread across many tables, increase the setting. Its maximum is 32.innodb_purge_threads is a non-dynamic configuration option, which means it cannot be configured at runtime.
爲了控制這個特性，增加配置選項innodb_purge_threads的值。如果DML操作集中在單個表或幾個表上，請將設置保持爲低，以便線程不會彼此競爭訪問繁忙表，如果DML操作分佈在多個表中，則增加設置。它的最大是32。innodb_purge_threads是一個非動態配置選項，這意味着它不能在運行時進行配置。
There is another related configuration option, innodb_purge_batch_size with a default value of 300 and maximum value of 5000. This option is mainly intended for experimentation and tuning of purge operations, and should not be interesting to typical users.
還有另一個相關的配置選項，innodb_purge_batch_size，默認值爲300，最大值爲5000。此選項主要用於試驗和調優purge操作，一般用戶對這個不應該感興趣
For more information about InnoDB I/O performance, see Section 8.5.8, “Optimizing InnoDB Disk I/O”.
有關InnoDB I/O性能的更多信息，請看 Section 8.5.8, “Optimizing InnoDB Disk I/O”.
PREV: 14.6.10 Configuring Spin Lock Polling https://blog.51cto.com/itzhoujun/2358047