Bug #36146 huge amount of memory required to layout tables

• Submitted: 16 Apr 2008 17:01
• Modified: 14 Jan 2009 15:08
• Reporter: Shane Bester (Platinum Quality Contributor)
• Status: Can't repeat
• Category: MySQL Workbench
• Severity: S4 (Feature request)
• Version: 5.0.19 SE
• OS: Windows
• CPU Architecture: Any

[16 Apr 2008 17:01] Shane Bester

Description:
Reverse engineering a database with 101 tables caused the mysqlworkbench.exe program to consume >230MB of memory.   This is a feature request to consider cutting down memory utilization.  Subsequently, a database with 1000 tables caused the workbench to crash after it consumed >1.8GB of ram and 100% cpu pegged for 20 minutes.

How to repeat:
import the attached file into mysql, and reverse the database. watch how much memory is consumed by mysqlworkbench.exe

Suggested fix:
any way to reduce memory consumption, and speed up the reversing so it doesn't peg the cpu at 100% for so long.

[16 Apr 2008 17:03] MySQL Verification Team

the schema i used.

Attachment: bug36146.sql (application/unknown, text), 284.05 KiB.

[16 Apr 2008 21:00] Sergei Tkachenko

The problem relates to layout of objects on the model rather than to reverse engineering as such. Layout is a standalone operation (can be accessed through main menu: "Model\Create diagram from catalog objects") parameterized version of which is included into reverse-engineering wizard for convenience.
Changed synopsis.

[14 Jan 2009 15:07] Susanne Ebrecht

Many thanks for writing a bug report. I can't repeat this behaviour by using Workbench 5.0.29 SE.

Please try again with newer release.