Shulou(Shulou.com)05/31 Report--

This article mainly introduces how to optimize innodb in mysql, which has certain reference value. Interested friends can refer to it. I hope you will gain a lot after reading this article. Let Xiaobian take you to understand it together.

innodb_flush_logs_at_trx_commit Is Innodb 1000 times slower than MyISAM and larger in head?

Maybe you forgot to change this parameter.

The default value is 1, which means that every committed update transaction (or statement outside of each transaction) is flushed to disk,

This is resource-intensive, especially when there is no battery backup buffer.

www.2cto.com

Many applications, especially those that have transitioned from MyISAM, can simply set it to 2,

That is, the logs are not flushed to disk, but only to the operating system cache. Logs are still flushed to disk every second,

Therefore, the consumption of 1-2 updates per second is usually not lost. If it is set to 0, it is much faster, but it is also relatively unsafe.

When MySQL server crashes, some transactions are lost. Set to 2 to direct the missing portion of the transaction flushed to the operating system cache.

Thank you for reading this article carefully. I hope that the article "How to optimize innodb in mysql" shared by Xiaobian will be helpful to everyone. At the same time, I hope that everyone will support you a lot and pay attention to the industry information channel. More relevant knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.