… data in primary key order into Innodb tables for optimal performance, but effect does not end here. If indexes are built by inserts in Btree order in which… history about loading similar data of similar size on similar hardware use that as estimate. If not use your best guess based…
Post: Tuning for heavy writing workloads
October 14, 2009 By 9 Comments
…innodb_flush_method = O_DIRECT (the followings are XtraDB specific general settings) innodb_ibuf_active_contract = 1 innodb_adaptive_flushing = false innodb_adaptive_checkpoint = estimate…in InnoDB…
Post: Why InnoDB index cardinality varies strangely
September 28, 2009 By 5 Comments
…with the index cardinality statistics reported by InnoDB tables. The cardinality varies because it’s derived from estimates, … aggregate them with counts: baron@kanga:~$ sort sizes | uniq -c 157 1022 156 1024 156 … not the only one who notices oddities in the random number generation. I waited. And …
Post: Finding your MySQL High-Availability solution – The questions
October 16, 2009 By 36 Comments
…technologies are by far, not a one size fits all and many deployments use … you are most likely using the InnoDB storage engine, since MyISAM is not… some features like Full text indexes and GIS indexes that are supported only by …as a few minutes in some circumstances. Yves’s estimate is for a project…
Comment: Learning about MySQL Table Fragmentation
May 12, 2008 By 20 Comments
Peter, Good catch though it does not have anything to do with table fragmentation. Simply if you’re querying number of rows in table for Innodb it performs estimation – this estimation requires several random dives in the clustered index, which causes IO for large table sizes.
