Reporting Services MemoryLimit

Question

Post reply

Reporting Services MemoryLimit

andrew@tregonning.net

SSCommitted

Points: 1503
More actions
October 23, 2006 at 3:36 pm

#174724
Hi
We're having trouble with memory configuration in Reporting Services 2k5 SP1, running on Win 2k3 SP1. We have a very large report, which we've been running to benchmark performance.
First, here are the results of our testing:
1. Initially, the server had 512mb of RAM. When running the report, the w3wp.exe process used up to 400mb of RAM and Reporting Services usually timed out before delivering the report.
2. We increased the RAM in the server to 1024mb, and found we could run the report. It took around 02'30" to complete, and the w3wp.exe process peaked at 520mb of RAM usage. When we tried to run two instances of the report concurrently, RAM usage peaked around 800mb, and Reporting Services timed out before delivering the reports.
3. Increasing the server RAM to 1536mb, we found could run two reports at once. It took around 04'05" to deliver the reports, and the w3wp.exe process peaked at 920mb of RAM usage. When we tried running three reports concurrently, RAM usage peaked around 1,220mb of RAM and Reporting Services usually timed out before delivering the reports.
4. Lastly, we put 2048mb of RAM in the server, and we could run three reports at once. It took around 06'58" to deliver the reports, and the w3wp.exe process peaked at 1,280mb of RAM usage. When we tried running four reports concurrently, RAM usage peaked around 1,290mb and Reporting Services died with a System.OutOfMemoryException exception.
The pattern we noticed with the first three steps, was that Reporting Services isn't using more than 80% of the physical RAM available on the server:
1. 400mb / 512mb = roughly 80%
2. 800mb / 1024mb = roughly 80%
3. 1,220mb / 1536mb = roughly 80%
4. 1,290mb / 2048mb = roughly 63%
Following the directions in "Configuring Available Memory for Reporting Services" (http://msdn2.microsoft.com/en-us/library/ms159206.aspx), we tried increasing the MemoryLimit of both the Web Service and the Windows Service.
We changed the memoryLimit in machine.config to:
<processModel autoConfig="true" memoryLimit="120" />
and the memoryLimit in rsreportserver.config to:
<MemoryLimit>120</MemoryLimit>
<MaximumMemoryLimit>140</MaximumMemoryLimit>
It looks like the ReportServer is reading this, as when it is restarting, the ReportServer_*.log file records:
w3wp!library!1!11/10/2006-10:20:56:: i INFO: Initializing MemoryLimit to '120' percent as specified in Configuration file.
w3wp!library!1!11/10/2006-10:20:56:: i INFO: Initializing MaximumMemoryLimit to '140' percent as specified in Configuration file.
However, it doesn't go above this 80% threshold.
More concerning is the System.OutOfMemoryException exception described above. Following the suggestions in KB 909678, we've tried tweaking the MemoryLimit and there is clearly still plenty of RAM left available on the server. This is happening repeatedly when we try to run four instances of the report concurrently.
Are there other parameters we should be adjusting to ensure Reporting Services uses the available RAM?
Thanks,
Andrew

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

debrucer1 SSCertifiable Points: 5366 More actions · Answer 1

curious, you are restarting RS... are you also restarting IIS?

Thank-you,
David Russell
Any Cloud, Any Database, Oracle since 1982

stevefromOZ SSC-Forever Points: 43646 More actions · Answer 2

Am also curious about this issue. When you say the report is 'large' just how many rows are you trying to retrieve? What amount of formatting/logic is contained in the body of the report? Have you looked at your execution and trace logs to determine whether the bottleneck is occuring during execution or rendering? You mentioned you'd looked at the KB article -> as it suggests did/have you tried running the report but retunring it as csv (assuming you were trying for html previously)?

Steve.

andrew@tregonning.net SSCommitted Points: 1503 More actions · Answer 3

Hi David

We're rebooting the whole server to add the new RAM, so yes, I am restarting IIS.

Thanks,

Andrew

andrew@tregonning.net SSCommitted Points: 1503 More actions · Answer 4

Hi Steve

When I say the report is large, I'm not kidding - the stored procedure returns about 180,000 rows.

The report contains a single matrix control, which does a GROUP BY, so I'm expecting the rendering to be fairly intensive on machine resources, however I rather it didn't just fall over!

Based on this excerpt from the ReportServer_<timestamp>.log, it looks like it dying during the rendering:

w3wp!library!1!10/25/2006-16:43:57:: i INFO: Call to RenderFirst( '/Testing/Monthly Pay Detail' )

w3wp!library!5!10/25/2006-16:43:59:: i INFO: Call to RenderFirst( '/Testing/Monthly Pay Detail' )

w3wp!library!7!10/25/2006-16:44:23:: i INFO: Call to RenderFirst( '/Testing/Monthly Pay Detail' )

w3wp!runningjobs!8!25/10/2006-16:44:30:: i INFO: Adding: 2 running jobs to the database

w3wp!library!8!10/25/2006-16:45:00:: i INFO: Call to RenderFirst( '/Testing/Monthly Pay Detail' )

w3wp!runningjobs!9!25/10/2006-16:45:31:: i INFO: Adding: 2 running jobs to the database

w3wp!processing!1!10/25/2006-16:52:20:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing., ;

Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing. ---> System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.

at Microsoft.ReportingServices.ReportProcessing.MatrixInstance.AddCell(ProcessingContext pc, NonComputedUniqueNames& cellNonComputedUniqueNames)

at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeMatrixGroupLeafObj.CreateOutermostSubtotalCell(MatrixInstance matrixInstance)

at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeMatrixGroupLeafObj.CreateSubtotalOrStaticCells(MatrixInstance matrixInstance, RuntimePivotGroupRootObj currOuterHeadingGroupRoot, Boolean outerGroupingSubtotal)

at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeMatrixHeadingsObj.CreateInstances(RuntimeDataRegionObj outerGroup, ProcessingContext processingContext, MatrixInstance matrixInstance, Boolean outerGroupings, RuntimePivotGroupRootObj currOuterHeadingGroupRoot, MatrixHeadingInstanceList headingInstances, RenderingPagesRangesList pagesList)

at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeMatrixGroupLeafObj.CreateInnerGroupingsOrCells(MatrixInstance matrixInstance, RuntimePivotGroupRootObj currOuterHeadingGroupRoot)

at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeMatrixHeadingsObj.CreateInstances(RuntimeDataRegionObj outerGroup, ProcessingContext processingContext, MatrixInstance matrixInstance, Boolean outerGroupings, RuntimePivotGroupRootObj currOuterHeadingGroupRoot, MatrixHeadingInstanceList headingInstances, RenderingPagesRangesList pagesList)

at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeMatrixGroupLeafObj.CreateInstance()

at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeGroupLeafObj.Traverse(ProcessingStages operation)

at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeGroupLeafObj.TraverseAllLeafNodes(ProcessingStages operation)

at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeGroupingObj.Traverse(ProcessingStages operation, Boolean ascending)

at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeGroupRootObj.CreateInstances(ReportItemInstance riInstance, IList instanceList, RenderingPagesRangesList pagesList)