Mess with innodb_thread_concurrency (mysql与多cpu)

chinalinuxzend

于 2009-02-03 17:46:00 发布

阅读量4.1k

点赞数

分类专栏： mysql分表 mysql服务器管理优化文章标签： concurrency thread mysql performance encoding bugs

mysql服务器管理优化同时被 2 个专栏收录

116 篇文章

订阅专栏

mysql分表

15 篇文章

订阅专栏

MySQL 5.0.19中innodb_thread_concurrency变量的意义发生了变化。设置为0表示不受限制的并发线程数。从5.0.8开始，默认值为20，设置大于等于20将禁用并发检查。但在5.0.19中，又回到了默认值8，而0禁用了并发检查。若之前设置超过500或使用默认值，在新版本中需改为0以避免性能下降。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

原贴:http://www.mysqlperformanceblog.com/2006/05/12/mess-with-innodb_thread_concurrency/

Mess with innodb_thread_concurrency

Posted by Vadim

In MySQL 5.0.19 the meaning of innodb_thread_concurrency variable was changed (yeah, again).

Now innodb_thread_concurrency=0 means unlimitied count of concurrent threads inside InnoDB. It’s logical, but there was long way. In MySQL versions below 5.0.8 for unlimited threads you had to set innodb_thread_concurrency over 500 (and default value for innodb_thread_concurrency was 8 ).

Starting with MySQL 5.0.8, the default value is 20, and concurrency checking will be disabled if the setting is greater than or equal to 20. But due to different bugs, in 5.0.19 the default value is 8 again, and 0 disables concurrency checking.

So if you used innodb_thread_concurrency over 500 (or default value in 5.0.8-5.0.18), don’t forget to change it to 0 in new versions, otherwise you can experience leaps of performance.

Posted by Vadim @ 2:29 am :: Innodb

Print This Post book mark Mess with innodb_thread_concurrency in del.icio.us

del.icio.us :: submit Mess with innodb_thread_concurrency to digg.com

digg
Comment RSS :: Trackback URI

1 Comment »

1. MySQL Performance Blog » InnoDB thread concurrency

[...] So what is the best value for innodb_thread_concurrency? For 1-CPU and 2-CPU I think it can be just disabled (innodb_thread_concurrency=0 since 5.0.19, more about default values). [...]

Pingback :: June 5, 2006 @ 2:33 am