June 18, 2013

Post: Percona Server 5.6.11-60.3 first Release Candidate now available

… Server for MySQL version …InnoDB heap allocation. This may improve write performance for high levels of concurrencyinnodb_data_home_dir variable… TABLE_STATISTICS, THREAD_STATISTICS, …INNODB_CHANGED_PAGES query started returning data to indicate an incomplete result set. Bug fixed #1185040. The INNODB

Post: Percona XtraDB Cluster 5.5.30-23.7.4 for MySQL now available

…fixed #1130888 (Seppo Jaakola). If MySQL replication threads were started before running wsrep …XtraBackup indefinitely when xtrabackup tmpdir was set up on tmpfs. Bug fixed #1086978… (Alex Yurchenko). If variable innodb_thread_concurrency has been defined to throttle InnoDB access, and work load…

Post: Percona Server for MySQL 5.5.30-30.2 now available

MySQL has implemented priority connection scheduling for the Thread Pool. (Alexey Kopytov) Percona Server for MySQLMySQL has fixed a number of performance bugs. (Alexey Kopytov) Drop table performance feature has been removed and its controlling variable innodb…in InnoDB high-concurrentset in…

Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue

MySQL has implemented priority connection scheduling for the Thread Pool. (Alexey Kopytov) Percona Server for MySQLMySQL has fixed a number of performance bugs. (Alexey Kopytov) Drop table performance feature has been removed and its controlling variable innodb…in InnoDB high-concurrentset in…

Post: InnoDB thread concurrency

threads) thread thrashing could be still observed even with limited innodb_thread_concurrency. This is why innodb_commit_concurrency variable was added in MySQL 5.0 innodb_commit_concurrency

Post: thread_concurrency doesn't do what you expect

thread concurrency inside MySQL with the variable thread_concurrencyinnodb-concurrency-tickets/ innodb_thread_concurrency places a limit on the number of threads that can be running inside InnoDB

Post: Mess with innodb_thread_concurrency

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

Post: MySQL 5.5 and MySQL 5.6 default variable values differences

innodb_thread_concurrency this will reduce overhead associated with grabbing and releasing innodb_thread_concurrency slot but will increase potential starvation of queued threads

Post: Ultimate MySQL variable and status reference list

innodb_strict_modeblogpercona.commanual innodb_support_xablogpercona.commanual innodb_sync_spin_loopsblogpercona.commanual innodb_table_locksblogpercona.commanual innodb_thread_concurrencyblogpercona.commanual innodb_thread_sleep_delayblogpercona.commanual Innodb

Post: Tuning InnoDB Concurrency Tickets

…that this variable only comes in to play when innodb_thread_concurrency is greater than zero. On a stock install of MySQL, …InnoDB is limited by innodb_thread_concurrency (which is why these two variables are most often tuned in concert). To continue the example, if innodb_thread_concurrency is set