We are using Stimulsoft in a load balanced and 'n-tiered' ASP.NET application. We experience a very slow performance, when we render reports using stiWebViewer. We have verfired that the database fetches are reasonably optimized and the performance block is within stimulsoft report rendering. We are looking through the following to examine if we can gain some performance benefits:
1. Add Stimulsoft DLLs to GAC
2. Cache the Database fetch results in the WEB layer, so that subsequent reloads need not fetch the data afresh.
3. Set the rendering mode to use Cache
4. Not to use StiWebViewer and instead render the output as html.
It would be great, if some one helps us by letting us know if any of them will contribute to the performance gain or suggest any other area that we should look into.
Experiencing a very slow performance
Experiencing a very slow performance
Hi GoldSun,
Thank you.
This would not help. But NGen can help here.goldsun wrote:We are using Stimulsoft in a load balanced and 'n-tiered' ASP.NET application. We experience a very slow performance, when we render reports using stiWebViewer. We have verfired that the database fetches are reasonably optimized and the performance block is within stimulsoft report rendering. We are looking through the following to examine if we can gain some performance benefits:
1. Add Stimulsoft DLLs to GAC
Although Ajax also consumes some of system resources such as holding of the users requests here this way also will not bring the faster rendering.2. Cache the Database fetch results in the WEB layer, so that subsequent reloads need not fetch the data afresh.
This way is a workaround for huge reports. Also is not applicable for improving of the performance.3. Set the rendering mode to use Cache
It is a brilliant idea. StiWebViewer is a component for interaction with a user. It consumes resources and avouding of this component would result in much faster rendering.4. Not to use StiWebViewer and instead render the output as html.
Please also avoid the compilation process as it also consumes time and resources. A workaround is to store reports in dlls or cs or vb files.It would be great, if some one helps us by letting us know if any of them will contribute to the performance gain or suggest any other area that we should look into.
Thank you.
Experiencing a very slow performance
Thank you Edward. We will make sure to avoid the compilation process.