Bug #72208 Item of "Performance Reports" was decreased.
Submitted: 2 Apr 2014 11:37 Modified: 8 Apr 2014 17:25
Reporter: Yoshiaki Yamasaki Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S3 (Non-critical)
Version:MySQL Workbnech 6.1.4 OS:Any
Assigned to: CPU Architecture:Any

[2 Apr 2014 11:37] Yoshiaki Yamasaki
Description:
Item of "Performance Reports" was decreased. The detail is as follows.

[MWB 6.1.2]
I can see following items.
 - Hot Spots for I/O
 - High Cost SQL Statements
 - Database Schema Statistics
 - Wait Event Times(Expert)
 - InnoDB Statistics

[MWB 6.1.3 and 6.1.4]
I can only see following items.
 - High Cost SQL Statements
 - Database Schema Statistics

I'll send the capture of GUI.

How to repeat:
Check "Performance Reports" via MySQL Workbench.

[environment]
 - Windows7
 - MySQL Workbench 6.1.4
 - MySQL 5.6

Suggested fix:
Return item of "Performance Reports" as same as MySQL Workbench 6.1.2.
[2 Apr 2014 11:38] Yoshiaki Yamasaki
"Performance Reports" at MySQL Workbench 6.1.2

Attachment: MWB_6.1.2.png (image/png, text), 143.55 KiB.

[2 Apr 2014 11:38] Yoshiaki Yamasaki
"Performance Reports" at MySQL Workbench 6.1.4

Attachment: MWB_6.1.4.png (image/png, text), 131.35 KiB.

[2 Apr 2014 15:20] MySQL Verification Team
PF Reports

Attachment: pf_reports.png (image/png, text), 113.19 KiB.

[2 Apr 2014 15:21] MySQL Verification Team
I couldn't repeat when connected to 5.6 server see prior attached picture. Thanks.
[4 Apr 2014 9:40] Yoshiaki Yamasaki
diff about sys_56.sql between "MWB 6.1.2" and "MWB 6.1.4"

Attachment: diff.htm (text/html), 57.32 KiB.

[4 Apr 2014 9:40] Yoshiaki Yamasaki
I solved this problem. The procedure is as follows.

 1.Execute "drop database sys;"
 2.Install sys schema from MWB(MySQL Workbench).

I created sys schema from MySQL Workbench 6.1.2 and I checked the Performance Reports from MWB 6.1.4.

I found the diff about sys_56.sql between "MWB 6.1.2" and "MWB 6.1.4".(Please check attached picture)
I think cause of this problem is this.
[8 Apr 2014 17:25] MySQL Verification Team
Thank you for the feedback.