Francesco Casella
Francesco Casella
OK, then I'm closing this ticket. Feel free to reopen it if there are further issues.
@perost can you please do some profiling and see where the bottleneck is?
@adeas31 please check if there is something simple you can do to improve this, in which case we may sneak it in 1.22.2, or if it requires some substantial re-design....
@ceraolo, @abuntrock we discussed this topic during today's developer's meeting. As noted by @perost, the problem with all these operations is that once the model has been changed, it is...
Not really, I'm afraid performance improvements will have to wait for the next release, for the next couple of weeks I would focus on quick fixes.
This is definitely very high-priority for us. Just not for the next release, which is basically tomorrow 😃
OK, so we have a number of operations on a diagram: - adding a component - duplicating a component (Ctr-C Ctrl-V) - removing a component - adding a connection -...
Discussion: - removing a component - adding a connection - removing a connection doesn't really need calling `getModelInstance()`, so we can remove it right now. If one removes a component...
For adding/duplicating, design in progress to instantiate the new component by itself, with information from the top level model, particularly if it has inner components. This will go in 1.24.0
Long term option: determine what parts of the instance tree are affected, and only re-instantiate those parts. Alternative: minimal instantiation (only the stuff which is relevant for display) Alternative: shallow...