Hello Infragistics,
I think the reporting feature that comes with the Infragistics WPF toolkit is a great idea. The API is easy to use and the xamFeatureBrowser explains the rest. Basically it's exactly what's needed to create some sophisticated reports.
Our software requirements ask for quite complex reports, using multiple grids, resulting in a number of pages usually between 10 and 30. Performance is an issue. I tried to print one XamDataGrid with about 90 rows and 50 columns and the rendering takes about 2 minutes. I think the slow performance mainly relates to the pagination of the grid (mosaic and vertical mode).
Obviously splitting a grid up to fit on a predefined page size takes some time, which is ok. My question is: How can I influence to document rendering processing time. Are there any hints from your side (similar to the performance optimizations overview for the grid). The grid is populated form a dynamic data source. The field layout is generated on the fly. Maybe I miss some settings to improve the printing performance. Do you have guideline, checklist?
Any help is highly appreciated.
Best regards, Frank
Hello Frank,
I see a difference in the performance between the different pagination modes, but it works much faster on my end. I created a XamDataGrid with 90 records and ~50 fields. With Mosaic horizontal pagination mode the XamReportPreview generates a report for 30~32 seconds. With Scale, the same XamDataGrid's report is generated for 14~15 seconds. I am testing this against the latest service release for 10.1 under Windows 7 on a Core 2 Duo (2.5Ghz) processor with 4Gb ram.
Are there any other settings that you have set on the report? What are your environment parameters?
Hi,
We are facing a similiar problem with the printing API performance. We make embedded visual report section using StackPanel with page height calculated and cropped images. All cropping and making of the ReportObject logic consumes 30% of the total time taken to print. The rest of the 65-70% of the time is utilized by the print/printpreview call of the report object. When doing a line level profiling, we find that the print call writes the report to an XPS document and then paginate and print.
Since we do calculation logic to create report object sections which fit into a target page size, Is there any part of the Infragistics logic that can be optimized. I mean can we turn some flag off so that the printing happens faster.
I tried to change the Horizontal pagination mode as discussed above, it does not have any effect on the speed.
We badly need some help to improve the printing performance.
-Alex