May 26, 2012

Post: Troubleshooting MySQL Memory Usage

Lock system 318875832 (318747272 + 128560) Recovery system 0 (0 + 0) Threads 425080 (406936 + 18144) Dictionary memory allocated 2623331 Buffer pool size 7864319 Buffer pool size

Post: Drop table performance

buffer pool, it may be a significant issue. This can get especially painful, as during this operation InnoDB holds the LOCKwas the Cisco UCS C250, the InnoDB buffer_pool size was 144GB, and I filled the buffer pool with

Post: Improved InnoDB fast index creation

tables | 0.000118 | | System lock | 0.000007 | | setup | 0.000027 | | creating table | 0.002255 | | After create | 0.000050 | | copy to tmp tablebuffer pool. A benchmark is worth a thousand words, so let’s repeat the last test with innodb_buffer_pool

Post: XtraDB/InnoDB CPU bound benchmarks on 24cores server

with InnoDB plugin, Xtradb-1.0.2-1, and XtraDB-1.0.2-2 (rel2). XtraDB-rel2 has notinnodb_additional_mem_pool_size=16M innodb_buffer_pool_size=15G innodb_data_file_path=ibdata1:10M:autoextend innodb_file_per_table=1 innodb_flush_log_at_trx_commit=2 innodb_log_buffer_sizelocks and to buffer_pool

Post: Heikki Tuuri answers to Innodb questions, Part II

with good results. I just wrote the post on this this matter the other day – choosing innodb_buffer_pool_sizelocks and reorganizes small portions of table online. Q38: Seems that adaptive hash indexes are not used for primary key lookups or not

Post: Performance problem with Innodb and DROP TABLE

with large buffer pool. Worst of all this is done while table_cache lock is being held so no other queries can start. This wasinnodb_buffer_pool sizewas 10 times better with single tablespace, though this will vary a lot depending on buffer pool size. MyISAM tables creating/dropping was

Post: Innodb Performance Optimization Basics

not swap out MySQL out of memory. MySQL Innodb Settings The most important ones are: innodb_buffer_pool_sizetables use this option, so you will not have uncontrolled innodb main tablespace growth which you can’t reclaim. This option was… especially in locking in 5.0 and even more to come with MySQL 5…

Post: SHOW INNODB STATUS walk through

tables used by transaction in question (meaning it was accessed) and number of tables locked by transactions. Innodb does not lock tables for normal operation so number of tables locked

Post: Heikki Tuuri Innodb answers - Part I

buffer pool. Though full table scan is only one of replacement policy optimizations possible. Q8: How do you assess current state of Innodb scalability withInnodb so it unlocks (or never locks) the rows if they were not matched by query where clause when it was not

Comment: MySQL Server Memory Usage

innodb_table_locks=0 innodb_buffer_pool_size=1800M # USE ALL MEMORY AVAILABLE #innodb_log_buffer_size=8M # Lowered from 32M according to MySQL innodb_additional_mem_pool_size=20M innodb