Localreport PDF export memory load
I'm running into (another) severe problem with LocalReport PDF exports: when the report contains a (or some) large charts, the memory load on the web server when exporting to PDF is enormous.
The report viewer uses some 5 MB to generate the report. Export to Excel does not have an observable effect. Then you export to PDF, and the w3wp allocates some more 500 MB of memory! Of course only when it can. Otherwise, you get an OutOfMemoryException. Ouch. Or the woker process is recycled. This is a catastrophe. Session state gets lots. Cache is gone. The app is unresponsive for some time.
"Large chart" means "large" in the sense of "taking space", not complexity. It does not matter at all what is displayed, a white reactangle will do. This leads me to the idea that this topic might be related to the PDF compressionbug"next version feature".
