I downloaded the new pre-release from your website.
We use the StiSLViewerControl via WCF-Service the complete Report is transfered to the client.
My last problem has beend solved with the new pre-release, I hope you can help me again.
When we open a report with about 20 pages it takes very long.
The CPU is running at 100% for a very long time, all 8 cores on a i7 are used, although the server should do the work at this time, because the WCF Call isn't completed yet.
We have deployed our application in the Microsoft Azure Cloud on an extra large instance, because we thought that our notebooks are too slow --> Cloud parameter 8x1,6GHz, 14GB RAM but there were no decreases of time it was even slower, the client worked longer at 100% CPU.
The report is filled over a datasource and a stored procedure, which is very quick --> over 2k rows in under 1 second. No sorting inside the report, just some styling and filling from the datasource.
Now we are searching for the bottleneck, because our customers do not except this behavior.
They have to wait a very long time, and CPU is running many seconds at 100%.
I hope you have a hint for us, where the bottle neck is, because this is an unacceptable behavior of the report rendering engine.
Here are some pictures of the taskmanger:
Taskmanger while using the report engine in the cloud:
Taskmanger while using the report engine locally:
Kind regards,
Daniel