Hello,

I am in the beginnings of a CPU profiling for our application, and I notice that the MeasureOverride(Size) takes up a lot of computing power.

It is called while loading up a rather large diagram (500+ nodes and 400+ links divided into 20+ child diagrams).

When going through the stacktrace, it goes extremely deep into the System.Windows component.

Do you have any idea as to why this method would eat up so much processing power per call?

Greetings,
Kim

Hi,

Adding to that, DiagramItem.MeasureOverride simply returns item.Bounds.Size by default, but if you use custom templates or DaigramNodeAdapter, it will actually delegate to the wrapped template visual / WPF element. I guess some optimization we could achieve is not calling Diagram.MeasureOverride the 8 times shown on your screenshot - but what do you mean by child diagrams and loading a diagram?

Regards,
Slavcho
Mindfusion

Hi,

Are these nested diagrams actual Diagram instances or some kind of group / container nodes? If I create a bunch of ContainerNodes from window constructor, MeasureOverride gets called just once in my test. You could override it in custom diagram class and add a breakpoint to check what exactly triggers the multiple MeasureOverride calls in your app.

Regards,
Slavcho