mysqlreport v3.4a is ready which, like the recently released v3.4, fixes a bug in the relative reports. This time, it was the InnoDB reports which were not correct when made relative. Changes in v3.4a are:
- Fixed bug: InnoDB report values were wrong in relative reports because 13 InnoDB status values needed to be excluded from being made relative. (thanks Debbie)
- Changed InnoDB Buffer Pool Read ratio to Read hit %
The Guide to Understanding mysqlreport has been accordingly updated, too.