摘抄老叶的文章，影响dml操作的一个因素

看到老叶的一个文章，其中提到了
innodb_max_purge_lag | 0 |
| innodb_max_purge_lag_delay | 0
两个参数，
Defines the maximum length of the purge queue. The default value of 0 indicates no limit (no delays).

Use this option to impose a delay for INSERT, UPDATE, and DELETE operations when purge operations are lagging (see Section 14.3, “InnoDB Multi-Versioning”).

The InnoDB transaction system maintains a list of transactions that have index records delete-marked by UPDATE or DELETE operations. The length of the list represents the purge_lag value. When purge_lag exceeds innodb_max_purge_lag, INSERT, UPDATE, and DELETE operations are delayed by at least 5000 microseconds. The delay calculation is (purge_lag/innodb_max_purge_lag - 0.5) * 10000.

To prevent excessive delays in extreme situations where purge_lag becomes huge, you can limit the delay by setting innodb_max_purge_lag_delay. The delay is computed at the beginning of a purge batch.

如果设置了，会对dml有影响

mysql purge的说明