June 19, 2013

Post: Heikki Tuuri answers to Innodb questions, Part II

innodb_buffer_pool_size Q36: There have been several MySQL bugs opened about multi-core scalability (concurrent queries, autoincrement, concurrent inserts, instrumentation, etc.). Rather thanbuffer pool? PZ: I guess it may be bug in the status

Post: MySQL 5.6 vs MySQL 5.5 and the Star Schema Benchmark

buffer pool. For this workload with a small buffer pool (the buffer pool is smaller than the working set) having innodbbuffer pool in pages afterwards: mysql> select sq.*, pages / (@@innodb_buffer_pool_size / 16384) * 100 pct_buffer_pool

Post: SHOW INNODB STATUS walk through

buffer pool is sized well – if you have constantly a lot of pages free, it probably means your active database size is smaller than allocated buffer pool size

Post: Why you should ignore MySQL's key cache hit ratio

buffer hit ratio, and a host of smallerSTATUSInnoDB tuning? You might be wondering, what about InnoDB tuning? What is the best way to choose an innodb_buffer_pool_sizesystem‘s capabilities. MySQL doesn’t have good instrumentation for scientifically choosing a key_buffer_size

Post: Wanted: Better memory profiling for MySQL

system and find MySQL using too much memory. I would look at memory consumed by Innodb (it is often higher than innodb_buffer_pool_sizesmaller fraction. Now. There are a lot of guesses I can make. Could it be memory allocated for per connection buffers… similary to SHOW STATUS – threads could account…

Post: Helgrinding MySQL with InnoDB for Synchronisation Errors, Fun and Profit

….61) and a single test, innodb_plugin.innodb_bug53674. The test is chosen for…buffer pool stats, the I/O stats might be slightly smaller than they should be. ==9090== Possible data race during write of size…: show_status_array(THD*, char const*, st_mysql_show_var*, enum_var_type, system_status_var*, …

Post: How Percona does a MySQL Performance Audit

… or smaller than normal, …system I’m working with. System performance Next I investigate what the systemInnoDB buffer pool is set to 22GB, it’s much easier to see 22GB thanstatus values for Created_tmp_tables and Created_disk_tmp_tables, I’ll paste in mysql> show global variables like ‘%table_size

Post: How much memory Innodb locks really take ?

Innodb row level locks are implemented by having special lock table, located in the buffer poolsize 503104 MySQL thread id 7429, query id 24542 localhost root show innodb statussystems. Furtermore you would unlikely need or want to lock every row in your table/database which makes it even smaller