May 24, 2012

Post: Heikki Tuuri Innodb answers - Part I

Innodb secondary Indexes trees are allocated in two extents same as primary key tree or stored in the same extent ? HT: An InnoDBnext index page in the ascending order is. InnoDB has a similar heuristic for descending index scans. The InnoDB

Post: Index lock and adaptive search - next two biggest InnoDB problems

…it’s going to be next biggest issues to make InnoDB scaling on high-end …index->lock mutex. InnoDB uses single mutex per index, so when you run mixed read / write queries, InnoDB locks index …. With disabled adaptive index InnoDB needs to perform much more operations reading secondary keys. How it …

Post: Another scalability fix in XtraDB

… fixes in InnoDB and also Google’s and your SMP fixes almost made InnoDB results acceptable in primary key lookups queries, but secondary indexes were… read-write lock. The new results you can see on graph. The patch for page_hash will be included in next release… InnoDB was run with next parameters: –max_connections=3000 \ –table_cache=2048 \ –query_cache_size=0 \ –innodb_data_file_path=ibdata1:100M:autoextend \ –innodb

Post: Scaling problems still exist in MySQL 5.5 and Percona Server 5.5

…, 62744144, 62744146) With secondary key defined…lock_s_lock_spin,pfs_rw_lock_s_lock_fu nc,btr_search_build_page_hash_indexnext,QUICK_RANGE_SELECT::get_nextindex makes things a lot worse in this workload and innodb_adaptive_hash_index_partitions=16 available for partitioning adaptive hash index