MySQL Bugs: #69184: Workbench performance issue

Bug #69184	Workbench performance issue
Submitted:	9 May 2013 12:48	Modified:	4 Nov 2014 4:32
Reporter:	Stefan Martinov	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S5 (Performance)
Version:	6.0.7	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	many tables, performance, workbench

Description:
When altering anything in the diagram the mysql begins to slow down. The slowdown process is much faster when elements inside of layers are being modified. The slowdown increases exponentialy. 

After 20+ changes the model needs to be re-opened to continue working on it since simple operations (adding a column) take several seconds to complete.

How to repeat:
Create 50+ tables in a diagram and start modifying the tables. The decrease in perforrmance should be notable.

Suggested fix:
n/a

Thank you for the bug report. Looks like duplicate/related of http://bugs.mysql.com/bug.php?id=68839 . Please check. Thanks.

Hello, 

thank you for your fast answer however the issue of the related bug is to memory consumption when idle whereas my issue is in a performance drop. When new elements and items are added, there are processor spikes. After every action the next action takes more and more time until simple moving of element to another position requires 4-5 seconds to perform.

Screenshot of processor performance when moving element inside layout left and right
http://d.pr/i/YU1G

Further notes:
The model i have has 270 tables and 9 diagrams

Thank you for the feedback. Please see http://bugs.mysql.com/bug.php?id=65688 too. Thanks.

Hello,

the bug is kind-of vague. I do not experience freezes like forever. The problem is the more actions i take the slower the application time is. 

If you move the model around, you don't experience slow-down at first. It's only in the later stages of modelling that you see the performance drop (in response time)

So it's more specific than the referenced bug!

Thank you for the feedback. Are you able to provide your model file (private if you wish) and the output of System Info?. Thanks.

Hello,

i am unable to provide the whole model since i am not allowed to. I am however allowed to give you the output file if you can direct me to it or provide any feedback needed.

What OS are you using? Can you at least provide a zoomed out screenshot of your diagram, so that we can have an idea of how many tables there are and their usage of layers etc, without being able to read anything?

http://d.pr/i/QpMh (One Diagram, there are 7-8 of diagrams)

However it seems not to be an issue with the newer version (The beta one)

Also i am using Windows 7 Professional

Please try version 6.0.7. Thanks.

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".

many-tables-database-model

Attachment: renamed-database.mwb (application/octet-stream, text), 631.25 KiB.

Sorry for the delay but i didn't see the message. Anyway, the issue is still active i 6.0.7 not so much with the memory usage, but with the degrading performance. 

I did however create a model that i am allowed to publish (with renaming) so you can check what is going on.

Currently rocking at around 500 tables.

Cheers,
Stefan

Have you been able to move forward on that behalf?

it has propagated through version 6.0.8 and 6.0.9

Do you need any more feedback?

Can you please provide information for the "Model undo history size" and "Auto-save model interval"? Values can be located in: Preferences -> General.

http://grab.by/utgW

Undo History Size : 25
Auto Save Interval: 1 minute

Thank you for the bug report.

Posted by developer:
 
performance increase confirmed in 6.2.4 using the model supplied in the report and comparing 6.2.3 vs. 6.2.4 build

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 6.2.4 release, and here's the changelog entry:

There was a performance regression between 6.0 and 6.1/6.2 when switching
diagram tabs, loading the model, as also adding new tables. The Catalog
Tree was refactored for increased performance.

Thank you for the bug report.