Having just moved Telerik Reporting Q3 2007 for a web application we have discovered that when a report is rendered then an attempt to export it as a pdf file is made then the w3wp.exe process is pushed to 100% cpu usage and a large increase in memory.
The amount of data in the report is relatively small and no graphics are being used, we are currently using LLblgenProDatasource2 as the datsource for the report.
At first we moved the application to a separate ApplicationPool in IIS 6 and increaded the max number of Threads available to the AppPool, while also turning on the ASP .Net State Service so Session State would work across the extra threads. This resulted in the curious effect where part of a report would render but data for sub reports wouldnt..... perhaps a separate problem with session state here?
The upshot is when running with inProcess session state a relatively small report with no graphical content will grind the server to a halt be overloading the w3wp process ...
any suggestions are most welcome ..
William Jack
The amount of data in the report is relatively small and no graphics are being used, we are currently using LLblgenProDatasource2 as the datsource for the report.
At first we moved the application to a separate ApplicationPool in IIS 6 and increaded the max number of Threads available to the AppPool, while also turning on the ASP .Net State Service so Session State would work across the extra threads. This resulted in the curious effect where part of a report would render but data for sub reports wouldnt..... perhaps a separate problem with session state here?
The upshot is when running with inProcess session state a relatively small report with no graphical content will grind the server to a halt be overloading the w3wp process ...
any suggestions are most welcome ..
William Jack