id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
2960	Extremely sluggish performance of OMEdit when browsing MSL and dragging components thereof	Francesco Casella	Adeel Asghar	"I have tried the following experiment on my Dell E7440 laptop, i5-4200U dual-core CPU, running OMC r23031 under Windows 7 Pro:
- Start OMEdit: it takes some time, but that's ok.
- Open a New Model: instantaneous action.
- Click on the Modelica package tree: top level packages show up quickly.
- Click on the Mechanics package tree: a few seconds and it shows up.
- Click on the MultiBody package tree: it takes 15 seconds to display the 12 sub-packages with their icons.
- Click on the Joints tree: it takes 1 minute 15 seconds (!!!) to display the 14 components and the three sub-packages.
- Open Modelica.Fluid.Vessels
- Drag one ClosedVolume onto the new model: it takes 25 (!) seconds for the new instance to actually get dropped on the new model diagram. This is particularly annoying as there is absolutely no feedback that anything is going on, unless one turns on the process monitors and sees that omc.exe is taking up a lot of CPU time.

This kind of performance is clearly unacceptable, give the very small amount of information that actually needs to be processed and ferried around between OMEdit and OMC to carry out these tasks. All this time is spent by omc.exe taking up two full logical CPUs out of four. It's nice that we get multi-threading, but to do what?

It seems to me that the implementation of the API functions called by OMEdit to gather the required information (or maybe the way they are called?) is extremely inefficient. Can you please investigate what is OMC doing all this time, and possibly find some fix?"	defect	closed	blocker	1.14.0	OMEdit	trunk	fixed		Adrian Pop massimo ceraolo