Application pool recycle on shared hosts

[Houssam Hamdan]

Hello all,

Even though we are using the pre-compiled assembly (.dll) form of the report, an application pool recycle is occurring thus clearing all active sessions.

On shared servers, the maximum amount of memory a worker process can consume before recycling the application pool is 64MB.

Please reply to the following:
- Is there a trick to minimize the amount of consumed memory ?
- If not, should we consider Stimulsoft libraries as bad candidate for shared hosts ?

Thank you in advance.

Cheers and regards,

PS: The report in question here is very basic. Just setting one variable value before export.

[Vladimir]

Hello,

Judging by the error, your server set the limit 64 MB of memory for the application. For the report generator it amount enough for the build only small reports, you need to increase the memory limit for applications.

Thank you.

[Houssam Hamdan]

Hi Vladimir,

The shared server is refusing to increase the amount of memory we are allowed to consume.

We would like to know if shared servers would be taken into consideration in your next release.

Thank you for your cooperation.

[Andrew]

Hello,

A lot of resources are required for working the ASP.Net application.
Our site is written in ASP.NET manually without using the constructors and modules. If you set the memory limit to 64 megabytes, then this memory is enough for simultaneous rendering of only a few simple pages. With the current pressures on our website we have set a limit of 512 megabytes, and this is not always enough.

For rendering reports much more memory is required. You should consider the volume of all loaded assemblies, the data for the report, etc. If there are images in a report memory amount increases dramatically.
Therefore, 64 megabytes is almost nothing to generate reports. And we cannot do anything with this.

Thank you.