We are using AR 7 SP1 in a web application.
In use, we’ve had some reports seem to take much longer than we would think it should. So, I did some testing and timing.
This is just an example of one report.
* Testing was done through Visual Studio 2012 (so, through code) on my machine’s IIS.
* This is running in a web application.
* Uses flashviewer.
* I timed the Page_Load event and it is taking less than 00:00:00:40. (Less than .4 seconds.) (Meaning, pulling in the report and all the little things we’re doing in the Page_Load isn’t affecting the speed.)
* The report was 933 pages long and each page was decently full.
Time results:
* Running the stored procedure: 13 seconds
* Running the report: 17 seconds
* From the time the Internet Explorer viewer windows popped up to when the report actually showed: 2 minutes and 30 seconds.
I then ran the application in Internet Explorer straight to our server and then ran the report. From the time the viewer window pops up to when the report actually shows is still around 2 minutes 30 seconds, so no difference from when I ran it on my machine through code.
I also tested using the PDF viewer, and it was actually just a tad slower.
To further the testing, I had the pop-up window NOT show the report (didn’t assign the report to the viewer control), instead exported the report out to a PDF file. This took about 8 seconds. When I opened the PDF file with a PDF reader, it took about 10 seconds to load the PDF viewer and the entire PDF. So, exporting and viewing the file took about 18 seconds compared to 2 minutes and 30 seconds for the web viewer.
1) Am I correct in assuming that when we run the report via rpt.Run(), that is actually running and rendering the report and the viewer is JUST displaying the report?
2) Is this behavior normal?
3) Is there any way to speed this up?
4) Is the viewer shown in a Windows Form any faster than the viewer shown in a web application?
Thank you in advance for your assistance.
Michael