Hi,
I am suing following env & control in my application:
InfragisticsWPF3*.v11.1,.NET framework 3.5, WPF , C#, XP
Control : xamdatagrid
as shown in attached screenshot, GridViewPanelFlat.MeasureOverride(Size availableSize) shown as expensive call and in HOT category.
would like to know -
- Why this call is costly, what is call stack for this method
- Is there any alternate way or workaround to avoid calling this method?
I follow optimization guidelines provided on following link.
http://ko.infragistics.com/community/blogs/kiril_matev/archive/2010/10/26/optimizing-xamdatagrid-performance.aspx
Hello,
Thank you for your post. I have been looking into it and I can say that MeasuceOverride method is derived from the FrameworkElement and is used for measuring the size and positioning of the children of an element. It is expected for the method to use CPU time, since it is responsible for rendering the records and the cells of the XamDataGrid. Also the MeasureOverride method is not explicitly called by the code of the XamDataGrid. It is derived method that is called when an element needs to render its children, so we cannot control when the method will be called.
Hope this helps you.
Thanks for your reply,
can you suggest any tricks to improve performance in such case? apart from mentioned in http://ko.infragistics.com/community/blogs/kiril_matev/archive/2010/10/26/optimizing-xamdatagrid-performance.aspx
Despite the suggestions given in that post there are approaches for improving the sorting, grouping and filtering of the XamDataGrid, by using external methods:
http://ko.infragistics.com/products/wpf/sample/data-grid/performance
As for the rendering I can say that our developers are trying to improve the performance with every next release.
It has been close to two years since this issue was posted and i see the same perf issue. Do you have any updates on how to improve performance here, The measure override is causing massive performance issue for us as well.