Prologika Forums

Teo,

I would like to ask your pointer again. We have seen very high mem usuage for w3wp.exe from task manager on the SQL Server which has Reporting Services running. The server is quad core, 16 gz ram, IIS is only used for reporting services. we have seen Peak Mem usuage 5,473,568 K, ReprtingServiceService.exe is actually only showing peak Mem Usuage of 140,224K. Apart from looking at the report design such as using sps, etc. Any place we need to tune at SQL Server and IIS. Since reporing services get blamed for slowing the server which I hate that.

Thanks

Don

The bad news is that there aren't many things you can do with SSRS 2000 and 2005 as far as memory management. The good news is that SSRS 2008 improves on memory consumption significantly.

Hi Teo,

Thanks again for the advices. I don't see any OOM exception, we do have one report taking way too long to return the data (6 min).

1. We do have two application pools, one for ReportManager, the other for ReportServer, I just check the property of the app pool, under "Recycling", we only check "Recycle worker processes (in min), and the value is default 1740 min. Do you suggest to check "Recycle worker process after consuming too much memory"? if yes, should I decide the value based on peak memory I see from the w3wp.exe?

2. Under "Performance", we don't have "Shutdown worker processes after being idle for" checked, we do check "Limit the kernel request queue", value 4000, should I check the "Shut down worker process after being idle"?

3. Should I make any changes at rsreportserver.config, MemoryLimit, RecycleTime, MaxMemory, etc.?

Thanks

Don

>I don't see any OOM exception, we do have one report taking way too long to return the data (6 min).

So, are the memory issues caused by this report only? Have you looked at the ExecutionLog table to find how much time is spent in data retrieval, processing, and rendering? Does the report have explicit page breaks defined? I'd suggest you spend some time understanding why the report is taking so much memory. I assume you use SQL Server x64.

1 and 2. I personally haven't run into memory-related performance issues so I cannot provide real-life experience here. But I don't think you should worry about the Report Manager domain. Performance counters will probably confirm this.

3. These settings apply to the Windows Service which is not the culprit here. This topic may help you.

One thing I'd try is testing the same scenario with SQL Server 2008 RC0 even if it's not on your radar yet. If it gives you much less memory utilization then there is no point trying to optimize something that cannot be optimized by design . I've found that RS 2008 yields significant memory savings with large reports.