…the number of unique pages the query accessed, the length of time query waited for row locks, etc)….No Tmp_table: No Tmp_table_on_disk: No # Filesort: No Filesort_on_disk: No Merge_passes: 0 # InnoDB…0.001414 # InnoDB_rec_lock_wait: 0.000000 InnoDB_queue_wait: 0.000000 # InnoDB_pages_distinct: 973 SET…
Post: Identifying the load with the help of pt-query-digest and Percona Server
December 29, 2011 By 3 Comments
Post: SHOW INNODB STATUS walk through
July 17, 2006 By 40 Comments
… active otherwise it will be zero. History list length 6 is number of unpurged transactions in undo … status could be “waiting in InnoDB queue” or “sleeping before joining InnoDB queue“. Latest one is quite interesting -… has to ensure data makes it to the disk – just passing it to OS cache is not …
Post: Ultimate MySQL variable and status reference list
January 8, 2011 By 4 Comments
…core_fileblogpercona.commanual Created_tmp_disk_tablesblogpercona.commanual Created_tmp_…delayed_insert_timeoutblogpercona.commanual delayed_queue_sizeblogpercona.commanual Delayed_writesblogpercona.commanual…max_join_sizeblogpercona.commanual max_length_for_sort_datablogpercona.commanual max…
Post: InnoDB: look after fragmentation
November 5, 2009 By 12 Comments
…=InnoDB Table has 11864696 rows and takes Data_length: 698,351,616 bytes on disk The problem is that after restoring table…_wait: 0.204893 # InnoDB_rec_lock_wait: 0.000000 InnoDB_queue_wait: 0.000000 # InnoDB_pages_distinct: 35584 You see that… not in buffer_pool and execution goes to read from disk Fragmentation by secondary key is much more likely than by…
