Chinaunix首页 | 论坛 | 博客
  • 博客访问: 2343540
  • 博文数量: 276
  • 博客积分: 5998
  • 博客等级: 大校
  • 技术积分: 5175
  • 用 户 组: 普通用户
  • 注册时间: 2010-12-24 14:43
文章分类

全部博文(276)

文章存档

2014年(25)

2013年(11)

2012年(69)

2011年(167)

2010年(4)

分类: Mysql/postgreSQL

2011-09-05 17:58:46

key_buffer_size + innodb_buffer_pool_size+max_connection*(sort_buffer_size+read_buffer_size+binlog_cache_size)+max_connection*2M
 
Warning

On 32-bit GNU/Linux x86, you must be careful not to set memory usage too high. glibc may permit the process heap to grow over thread stacks, which crashes your server. It is a risk if the value of the following expression is close to or exceeds 2GB:

innodb_buffer_pool_size + key_buffer_size + max_connections*(sort_buffer_size+read_buffer_size+binlog_cache_size) + max_connections*2MB

Each thread uses a stack (often 2MB, but only 256KB in MySQL binaries provided by Oracle Corporation.) and in the worst case also uses sort_buffer_size + read_buffer_size additional memory.

By compiling MySQL yourself, you can use up to 64GB of physical memory in 32-bit Windows. See the description for innodb_buffer_pool_awe_mem_mb in Section 13.2.3, “InnoDB Startup Options and System Variables”.

http://dev.mysql.com/doc/refman/5.5/en/innodb-configuration.html

阅读(1602) | 评论(0) | 转发(1) |
给主人留下些什么吧!~~