Hello
I'm working in a software that needs to show thousands of points (double, string). Also I need the ability to zoom and pan the data. The functionality can be easily reached with XamDataChart, but I'm experimenting an terrible performance issue. The strange thing is that the line of code that has the worst performance (perceived during a debug session) is as follows:
private XamDataChart Datachart;
....
DataChart.Series.Clear();
What you suggest? What else do you need to know?
Thanks
Tárik
Hi,
Do you have a lot of differenct series in the chart or just one? We've perceived an issue with this internally, but unfortunately the fix did not make it into the latest Service Release, and will have to wait for the next one. Are you running the latest Service Release? There have been some other performance improvements recently that should possibly help.
If you can share a project that simulates what you are doing, I can take a look at it and see if there is anything you can do as a workaround, and verify that the pending fix also alleviates your problem.
If the performance profile looks vastly different when you are in run mode, then the performance problem is likely just a lot of verbose binding information that WPF outputs as the markers are removed from the tree. It can create a performance lag on chart creation too. Run without the debugger attached to get a better idea of real world performance.
-Graham
Hi Graham
I'm really disappointed, with the performance. The worst is that occurs in Clear() method. I just need to say that the usability of my software is compromised by the Infragistics library. I'm already looking for an alternative vendor.
Regards
Graham
I tested your sample and found that it emulates well my scenario. The performance isn't good as it takes around 13s for complete the clear call. I don't think that I understand what you say about service release, I'm using the 10.3.20103.1003 DLL (InfragisticsWPF4.Controls.Charts.XamDataChart.v10.3) version, is that what are you talking about?
I'm working in your order suggestion and I'll reply soon.
The suggestion to dump the XamDataChart object and create another indeed make a really difference in performance. But I still expect the improvement because other functionalities still has the low performance: Zoom, Pan and Resize. It's a key feature of my software the user ability to interact with the chart to chose data for some further algorithm.
I didn't experience the 13 second delay with the sample I sent you with the current version of the code (the latest and greatest) but I also didn't seem to experience the delay with the latest publically available service release code. Let me check the version for you to see if you have the latest bits.
The latest service release for the 10.3 product has version numbers ending in 2096. I don't see any 13 second delay upon removal of the series in the sample I shared using these binaries. And I believe we have only improved the performance further since.
Are you using the trial version of the product? This is always the unpatched volume release version, at the moment. I think we are looking into ways to keep the trial version more current in the future. There have been considerable performance enhancements that have been released in version 10.3 after the initial Volume release (which is the version you are using, I believe).
If you have a license for the product. I encourage you to download the latest service release, as it appears to negate this particular performance problem: http://www.infragistics.com/dotnet/netadvantage/wpf/data-visualization.aspx#Downloads
And I'm aware of changes we are incorporating into the next service release that further improve this clearing scenario. It looks like the current projected ship date for the next Service Release for the 10.3 product is February 28th:
http://www.infragistics.com/support/service-releases.aspx#ServiceReleases
Hope this helps!
I use all the paid version of Infragistics Controls and DataVisualization for WPF. Now I understand what the numbers means and where I found them (download area of the user).
I tried the 2096 service release and the improvement was very impressive, but still exists some room for improvement.
Thanks for the support