Hi,
Can anyone tell me why it takes up to 2 sec. to expand one node of this hierarchical grid (attached sample)?
We have quite fast machines and we expect better performance from the xamdatagrid.
(Core 2 Quad with 4GB of RAM).
Thanks.
PS. Tried with version 9.1.2091 and 9.2.2001. Both have the problem.
Want to share another discovery I found which might help troubleshooting:
In the example solution and our own solution, if I expand the last record first, then expanding other records becomes fast. However, if you collapse the last record, then expanding/collapsing other records becomes slow again.
Want to share you with two discoveries that I made in case someone has more insight:
1. Yesterday the expansion was less than 1 second, that was with the default window size set in the application. If I maximize it to 1280x1024, then it does take almost 2 seconds; If I re-size it to 300x200, then it is almost INSTANT! So the performance is related to the viewable area of the window, and probably the number of columns as well.
2. I added RecordExpanding and RecordExpanded tracking and found the time spent between is minimal; however, there is some delay before RecordExpanding is being called.
So I imagine a workaround like this: expand the group as if the viewable area is small and then programmatically re-size to previous size. Don't know how to do it and if it's possible.
Thanks,
Yu
Anyone has update on this issue? We have similar performance issue and I found this post. When I ran it, it took less than 1 second which is similar performance to a grid we are developing now. But we all feel it is TOO slow. It should be instant. Still looking for a workaround.
Let me know if there's any update.
Thanks!
Thanks a lot.
I did profile the sample with AQTime and almost all the time is within ArrangeOverride and OnPropertyChanged of panels and presenters.
When we add our custom styles to the xamDataGrid, it takes up to 7-8 seconds to expand a node... but all the CPU time is still used in ArrangeOverride and OnPropertyChanged of several objects.
Let me know if the AQTime report could be of any help.
Hello,
I brought this up to the developer but we cannot seem to find any reason why this should be that slow. There are many child cells being generated but we will try to profile your sample and find a way to optimize this. I am going to open a support case on your behalf so that we will notify you when we resolve this.