Bug #43232 Workbench is slow when working with 30+ tables
Submitted: 26 Feb 2009 15:34 Modified: 5 Mar 2009 14:10
Reporter: Sebastien Yapo Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S5 (Performance)
Version:5.0.30 OS:Windows (Vista SP1)
Assigned to: CPU Architecture:Any
Tags: slow

[26 Feb 2009 15:34] Sebastien Yapo
Description:
MySQL Workbench becomes really slow if working with more than about 30 tables.
Any action takes more than 1s to be accomplished on a correct computer (Core 2 Duo 2GHz) rising CPU load to 100% during wait time.
This bug is related to Bug #38439 which is closed but the issue is still there.

MySQL Workbench OSS for Windows version 5.0.30
Cairo Version: 1.5.12
Rendering Mode: GDI Rendering
OpenGL Driver Version: Not Detected
OS: Windows Vista/2008
CPU: 2x Intel(R) Core(TM)2 Duo CPU     T7300  @ 2.00GHz, 2.0 GB RAM
Video adapter info:
Adapter type: Carte graphique VGA standard
Chip Type: GeForce 8600M GT
BIOS String: Version 60.84.62.0.29
Video Memory: 524288 KB

How to repeat:
Create a diagram with more than 30 tables.

Suggested fix:
As a temporary fix, reducing history size seems to be effective.
[27 Feb 2009 15:49] Susanne Ebrecht
Many thanks for writing a bug report. We know about the problem already. We will hope that it will be better with upcomming Workbench version 5.1.

The workaround for your problem is to shrink down undo limit to 5 or 10.
[5 Mar 2009 14:10] Susanne Ebrecht
We are already and continuous working on this topic. It already is better with Workbench 5.1 and will be better with Workbench 5.2 and 6.0.

Triage team decided to close this bug report because this kind of performance is an already known problem and is it is a permanent topic in QA tests.