Problem with PhysicalComponents about py-capellambse HOT 3 CLOSED

It works but very slowly

That is reassuring to read actually. :)

I found a model where I can repro, although it's not quite as bad as on your side (~8s). It seems that computing the PhysicalComponent.deploying_components becomes very slow very quickly as a model grows, because it has to search the model for backwards references (we currently can't keep track of those properly yet).

For the time being, until a proper solution is in place, I think it makes the most sense to skip these slow attributes in the display logic, so that they have to be displayed explicitly when needed.

from py-capellambse.

I can't seem to reproduce this with any of our models, displaying objects consistently takes less than a second for me. Could you post the full stack trace of the KeyboardInterrupt from your last screenshot? That should give us a hint at what it was doing that took so long.

from py-capellambse.

Following your comment, I have tried to look at the full stack trace of the KeyboardInterrupt and unfortunetly it is not reproducible. I have tried also to not interrupt the process. It took 1m38s for the instruction model.pa.all_components[0]. So It works but very slowly ! I's true that I have 300 PhysicalComponents in my model. Do you think it is only due to the model size ?

from py-capellambse.