MYSQL Set the cache correctly

innodb_buffer_pool_size should be about 70% of available RAM.

Negatives

Here are some things that are not likely to help performance. They stem from out-of-date information and/or naivety.

.InnoDB has improved to the point where MyISAM is unlikely to be better.

.PARTITIONing rarely provides performance benefits; it can even hurt performance.

.Setting query_cache_size bigger than 100M will usually hurt performance.

.Increasing lots of values in my.cnf may lead to 'swapping', which is a serious performance problem.

."Prefix indexes" (such as INDEX(foo(20))) are generally useless.

.OPTIMIZE TABLE is almost always useless. (And it involves locking the table.)

Conclusion

In this page (written and validated by A. Gawali) you learned about MYSQL Set the cache correctly . What's Next? If you are interested in completing MYSQL tutorial, we encourage you simply to start here: MYSQL Tutorial.

Incorrect info or code snippet? We take very seriously the accuracy of the information provided on our website. We also make sure to test all snippets and examples provided for each section. If you find any incorrect information, please send us an email about the issue: mockstacks@gmail.com.

Share On:

Mockstacks was launched to help beginners learn programming languages; the site is optimized with no Ads as, Ads might slow down the performance. We also don't track any personal information; we also don't collect any kind of data unless the user provided us a corrected information. Almost all examples have been tested. Tutorials, references, and examples are constantly reviewed to avoid errors, but we cannot warrant full correctness of all content. By using Mockstacks.com, you agree to have read and accepted our terms of use, cookies and privacy policy.