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.
Hello,
I tested this with 9.1.10091 on a lower performance machine and it looks normal. The record expands for about half a second. I will forward this to the developers if they have any feedback on the sample and will update this thread when I have more information on this.
It should be instant.
I tried to recompile the source code with x86 instead of AnyCPU, but the performance is the same.
Is there anything I can re-template to speed it up?
HI,
Our NetAdvantage 10.3 release will be addressing performance.
Here a help link to the roadmap
http://ko.infragistics.com/innovations/roadmap/wpf.aspx#WPF Here a help link to Peformance Optimizations Overview for the XamDataGrid http://help.infragistics.com/NetAdvantage/WPF/2010.2/CLR4.0/
Sincerely, MattDeveloper Support Engineer
That is good news that you are improving the performance of the grid
Because the performance of the xamdatagrid is very bad at the moment.
In my usage of the grid the standard wpf datagrid takes less than a second to refresh with a new set of data ( 30 rows, 9 columns 4 columns with combo boxes)
and the xamdatagrid takes 5-6 seconds to do the same refresh with the same data and setup. Excluding the custom colouring of cells that occurs on the wpf grid. 5-6 seconds is almost unusable.
I look forward to the new release with speed improvements
Regards
Murray
Hi Matt,
I tried the 2010.3 today and updated the sample application to use the new version. However, the expansion performance is still the same, I couldn't tell the difference between this and running it with 2010.2. Please raise the issue to development team and we still need further help on this issue... . Thanks, Yu
I don't see any difference too...
I will bring this issue to the attention of our developers Sincerely,
Matt Developer Support Engineer