Bug #44077 Workbench performance degrades when selecting table
Submitted: 3 Apr 2009 13:14 Modified: 7 May 2009 20:14
Reporter: Ken Brown Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.1.9 OSS Beta OS:Windows (Vista Ultimate)
Assigned to: CPU Architecture:Any
Tags: performance, tables, workbench

[3 Apr 2009 13:14] Ken Brown
Description:
When creating a lot of tables in a single session performance gradually deteriorates when selecting a table.  Columns show immediately but can take up to 15 seconds for the definition to be free to use. App shows as not responding during this time and overloads a processor (on AMD Turion 64) 

How to repeat:
Create new model
Create 50+ tables in a single session
Select tables for edit at random

Suggested fix:
None
[3 Apr 2009 16:15] MySQL Verification Team
Bug: http://bugs.mysql.com/bug.php?id=44078 has been marked as duplicate of this one.
[7 Apr 2009 10:12] Valeriy Kravchuk
Thank you for the problem report. Please, send the results of Help > System Info.
[7 Apr 2009 10:27] Ken Brown
MySQL Workbench SE for Windows version 5.1.9
Cairo Version: 1.5.12
Rendering Mode: GDI Rendering
OpenGL Driver Version: Not Detected
OS: Windows Vista/2008
CPU: 2x AMD Turion(tm) 64 X2 Mobile Technology TL-66, 3.3 GB RAM
Video adapter info:
Adapter type: ATI Radeon X1200 Series 
Chip Type: ATI Radeon X1200 Series (0x791F)
BIOS String: BK-ATI VER010.044.000.002.025007
Video Memory: 327680 KB
[7 Apr 2009 14:21] Valeriy Kravchuk
I can't repeat this with 64-bit XP having only 1G of RAM, 3GHz Xeon and much simpler Nvidia with 64M of video memory, even with 100+ tables... So, this is either Vista-related or ATI-related problem.
[7 Apr 2009 20:14] MySQL Verification Team
Thank you for the feedback. Are you able to provide the .mwb file which presents the issue reported?. Thanks in advance.
[7 May 2009 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".