Running reports in ASP .Net Core can easily bring the server to a crawl

[Paul West]

We created an ASP .Net Core application using Bold Reports Embedded components. If running a lengthy report, or more than one user runs a mid-length report (ie. 1000+ pages), the server becomes completely unresponsive until the report(s) complete(s). By unresponsive, I mean the server will not show the index page, we cannot RDP into the server, and all other processes on the server come to a crawl.

Is there any way to manage the server memory or generate reports in separate threads to maintain some sort of functionality. If the reports take a little longer to generate that will be acceptable, as long as the server remains responsive.

[Vinoth Srinivasan]

Hi Paul, 

Please refer the below documentation to improve the performance while exporting the report with large data. 

https://documentation.boldreports.com/javascript/report-viewer/faq/improve-the-performance-while-loading-report-with-huge-data/ 

Regards, 

Vinoth S. 

[Vinoth Srinivasan]

Hi Paul, 

Please ignore our previous update. 

In order get the better performance with Report Viewer, apply below setting in Report Viewer to handle the larger amount data with less memory footprint. 

reportOption.ReportModel.EnableVirtualEvaluation = true; 

reportOption.ReportModel.DisablePageSplitting = true; 

Also, set the CanGrow true for necessary textbox report items alone because if  report having larger amount of data, then it will take time to measure height and width for larger amount of textboxes. Please refer the below documentation for your reference. 

https://documentation.boldreports.com/javascript/report-viewer/faq/improve-the-performance-while-loading-report-with-huge-data/ 

Regards, 

Vinoth S.