We have a tree with 50k Elements.
Traversing the Tree and with a function similar to this results in significant worse runtime in 18.1 .
In 17.2 it finishes after about 5 seconds.
In 18.1.176 (nuget) it runs forever.
Checking the runtime with Stopwatch i found out that 99.99% of the time is spend in node.HasChildren.
"node.Nodes.Count > 0" is slow too.
private static void FindCorrespondingNode(XamDataTreeNodesCollection nodes, object value) { foreach (XamDataTreeNode node in nodes) { if (node.HasChildren) { FindCorrespondingNode(node.Nodes, value); } } }
Hello Jens,
Thank you for contacting Infragistics!
When I make a tree with 50k nodes and call HasChildren I am not experiencing long time. Can you please try updating to the latest service release of v18.1 which is 255.
The best way for us to assist you is if you provide a small isolated sample that we can run and use for debugging locally. If you are unable able to provide an isolated sample I may be able to give suggestions if you provide the code for your page.
Hi.
thanks for your reply.
Sadly we cannot use 255 because of another error in that release (CAS-198754-J7K8Z4)
i've attached an example which reproduces the problem.
You are correct. It seems to be fixed in 255.
176: 30 Second
255: 500 ms
5611.WpfApp1.zip
Thank you for the update. When you get the build that contains the fix for your other case it will also contain the fix for this issue. Depending on how blocking the issue is you could upgrade and then work around that until you can get a build so that this isn’t blocking you anymore.