May 30, 2012 at 6:19 pm
I am getting this exception "Out of Memory" in eventvwr while users are running reports. SSRS resides in same system as DB. So, this eventually freezes out evrything including the server. And users get error saying "report cannot be displayed". I could see that reportingservice was taking more than 1GB mem at that point.
I had to kill reportingservices.exe and start it to resolve this for the time being. After this, memory usage by SSRS came down to 200-300MB. This has happened 2 times this week and so now we have given a temp sol as we told users only to run very imp reports during prod time. (which users are not happy with) 🙁
On investigation, I could see that i can config mem for SSRS (http://msdn.microsoft.com/en-us/library/ms159206.aspx). But, I am not sure how effective is this. [it says, "If existing requests continue to consume additional memory after the WorkingSetMaximum value has been reached, all report server application domains will be recycled"]. So, not sure how that impacts the server / db / reports.
OS: Win 2008 64bit 12GB RAM
DB: SS 2008 R2 64bit - allocated 8.5GB memory
We are also looking at migrating this SSRS to another server so that we can have a dedicated DB server.
Any help / comments / suggestions on this is really appreciated.
Thanks in Adv,
MvM
May 31, 2012 at 2:15 pm
I'd definitely suggest adding a dedicated SSRS box. Until then I'd reduce the max memory for the SQL Server database engine to free up memory for SSRS and the OS.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
May 31, 2012 at 5:14 pm
Thanks a lot for your reply Jack.
But unfortunately I cant cut down sql server memory now as its hitting peak levels now itself.
As a temp solution, before SSRS migration im thinking of suggesting RAM upgrade to have more room for SS as well as SSRS.
Whats your take on that?
Thanks again !
May 31, 2012 at 5:27 pm
SQL Server is going to grab all the memory it can regardless of how much you put in there. If you add memory I wouldn't adjust the max memory setting for SQL Server until I had established a baseline using System Monitor of how much memory I had left at peak load.
Right now, just 3.5GB for OS, other applictions, and non-buffer pool memory for SQL Server is low, in my opinion, anyway. Check out Jonathan Kehayias' blog post, http://www.sqlskills.com/blogs/jonathan/post.aspx?id=2e9a460a-0dff-494c-87ba-fd35df180b7e, where for your SQL Server, if it was dedicated to SQL Server, he'd recommend leaving 4GB free and you have SSRS running.
Reducing the max memory for SQL Server which really only is the buffer pool memory, may slow down some thing, but it won't bring everything to a halt like is happening now.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
May 31, 2012 at 5:45 pm
Thanks Jack for your quick response.
I am looking into your suggestions.
In the meantime, how abt configuring mem for SSRS (http://msdn.microsoft.com/en-us/library/ms159206.aspx).
Thanks
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply