Is innodb_flush_logs_at_trx_commit optimized by mysql 1000 times slower than MyISAM? Maybe you forgot to modify this parameter. The default value is 1, which means that every update transaction committed (or a statement other than each transaction) will be refreshed to the disk,
This is quite resource-consuming, especially when there is no battery backup cache. Www.2cto.com many applications, especially those transformed from MyISAM, can set its value to 2,
That is, logs are not refreshed to the disk, but only to the operating system cache. Logs are refresh to the disk every second,
Therefore, the consumption of 1-2 updates per second is usually not lost. If it is set to 0, it will be much faster, but it is relatively insecure.
Some transactions are lost when the MySQL server crashes. Set to 2 to direct the part of the transaction that is lost and refreshed to the operating system cache. Author C ++ Technical Center