Don’tAssume–PerSessionBuffers
内容导读
互联网集市收集整理的这篇技术教程文章主要介绍了Don’tAssume–PerSessionBuffers,小编现在分享给大家,供广大互联网技能从业者学习和参考。文章包含1742字,纯文字阅读大概需要3分钟。
内容图文
![Don’tAssume–PerSessionBuffers](/upload/InfoBanner/zyjiaocheng/578/7f457f94b3284ea18e6adf6f7c0d1522.jpg)
Global buffers include:
- key_buffer_size – For MyISAM Indexes (note you can define multiple key_buffer’s The MyISAM Key Cache)
- innodb_buffer_pool_size – For Innodb Table/Indexs
- innodb_additional_mem_pool_size – Innodb additional data dictionary data
- query_cache_size – The MySQL Query Cache
The four important per session buffers are:
- read_buffer_size
- read_rnd_buffer_size
- sort_buffer_size
- join_buffer_size
I have seen people see these values > 5M. The defaults range from 128K to 256K. My advice for any values above 256K is simple. What proof do you have this works better? When nothing is forthcoming, the first move is to revert to defaults or a maximum of 256K for some benchmarkable results. The primary reason for this is MySQL internally as quoted by Monty Taylor – for values > 256K, it uses mmap() instead of malloc() for memory allocation.
These are not all the per session buffers you need to be aware of. Others include thread_stack, max_allowed_packet,binlog_cache_size and most importantly max_connections.
MySQL also uses memory in other areas most noticeably in internal temporary tables and MEMORY based tables.
As I mentioned, there is no bound for the total process memory allocation for MySQL, so some incorrectly configured variables can easily blow your memory usage.
References
- Read Buffer performance hit by Monty Taylor
参考:
http://ronaldbradford.com/blog/dont-assume-per-session-buffers-2010-03-08/
内容总结
以上是互联网集市为您收集整理的Don’tAssume–PerSessionBuffers全部内容,希望文章能够帮你解决Don’tAssume–PerSessionBuffers所遇到的程序开发问题。 如果觉得互联网集市技术教程内容还不错,欢迎将互联网集市网站推荐给程序员好友。
内容备注
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 gblab@vip.qq.com 举报,一经查实,本站将立刻删除。
内容手机端
扫描二维码推送至手机访问。