Hi,
Our company has already bought your Silverlight controls and we are thinking of buying your Silverlight visualization controls. However we do have a problem we encountered. We get an outofmemory exception if the hierarchy's are too big.
I followed your hierarchy code for creating hierarchy's with expanders and their aggregated totals. However, when I have 3 row fields(3 hierarchy levels) or more and try to expand all(using some of your code again to expand all hierarchy's) then I run into a outofmemory exception. I checked the task manager and memory for the silverlight client hit 1.6gigs before throwing that exception. Is there any fix for this? I'm guessing for how the hierarchy's work it is not using virtualization?
Many thanks,
Wai
Hello Wai,
NetAdvantage 12.1 should be available for download till the end of the month.
Thanks for your reply. I will be looking forward to version 12.1. Do you have an ETA for version 12.1?
Thanks
I can say that there is Virtualization, but it’s for the UI elements of the XamPivotGrid. The memory grows, because every time you expand a hierarchy the Total values are recalculate and new queries are executed. It’s a known issue and in version 12.1 the performance will be improved.
Hope this helps you.
Thanks for your reply,
I will try to get a sample out at home as i cant send any code out here at work. But it happens with your samples too check http://samples.infragistics.com/sldv/RunSamples.aspx?cn=pivot-grid#/pivot-grid/handling-large-data if you generate 500 records and keep on adding dimensions into the row and column fields and keep on expanding the hierarchy's, you will see in the windows task manager the silverlight container memory usage will reach 1.6gig and then crashes.
Regards,
Thank you for your post. I have been looking into it, but it seems like I am missing something about your scenario, so if this is still an issue for you, could you please send me an isolated sample project, where this is reproduced, so I can investigate it further for you.
Looking forward for your reply.