I clean delete all tables form the metadata database, in order to get new tables when metadataeditor starts up.
I save and give it a name.
I create a connection and load 100 tables. It takes 50 seconds to load it from an AS/400 DB2/400 database. Not fast but ...
When i save again it takes over 5 minutes to save the whole to the database.
Does anyone have better performance using mysql5?

The problem is in the Sun MDR logic. It uses tables to run the Metadata Object Facility (MOF).
Tables are dynamically created and destroyed to do so. That's causing the slowdown.
Personally, I would run on the local machine (from file) until I really had to push it into a MySQL repository.
Even safer is to export to XMI after everything is OK and then import it into the MySQL repository.

That way you can edit you models at ... euh... more reasonable speed.
BTW, this performance drop is the price we pay for going with the CWM model.
We are investigating alternatives, but it's a "nobody ever got fired for chosing CWM" situation ;-)

Take care,

Matt

marx

10-31-2007, 06:41 AM

Hi,
Could you elaborate a bit on "going with the CWM model" part. To my best understanding CWM is just a framework
(or a metamodel, if you wish) so I'd like to understand what do you mean by 'CWM model' here. Do you have any
technical details of your metadata implementation available? A whitepaper or an ER diagram perhaps?

Best regards,
marx

MattCasters

10-31-2007, 04:06 PM

CWM is indeed a metamodel. However, to persist/store a metamodel, you need to store it in a (Level 3) Metadata Object Facility, MOF.