Looking at the report server since we have one live on E10 and it seems to be steadly increasing its RAM usage. It’s now sitting at 27G, not sure if it’s level off or not.
Does it just continue to grow until it consumes all RAM unless you put in a limit, just like MSSQL Server?
Is this the ReportingServicesService.exe or the actual SQL database component of the Report Server? I am assuming the latter and typically do not recommend restricting it. However, if you run other applications on this server you might want to consider it.
We’ve ran into this issue before, it appears to be a bug in MSSQL Reporting… restarting SSRS Service will fix it, we haven’t found a permanent work around.
We have a process that restarts it if it hits a certain threshold for the time being.
Did you modify the RsReportServer.config file to limit the process and recycle?
Did you do the restart of the SSRS service while running live? I assume there wouldn’t be any issues doing that, just want to be sure.
I was running into that issue in SQL 2008 and 2012. Since we’ve been running SQL 2016 that hasn’t happened. I use this TSQL and then reset my memory:
EXEC sys.sp_configure N’show advanced options’, N’1’
RECONFIGURE WITH OVERRIDE
GO
EXEC sys.sp_configure N’min server memory (MB)’, N’0’
EXEC sys.sp_configure N’max server memory (MB)’, N’20480’/Set back to max ram/
GO
RECONFIGURE WITH OVERRIDE
GO
The post @Jonathan_Lang has will limit SQL Server memory consumption, which I typically let it manage but with caveats. The reporting services itself is a different animal and it does have mechanisms that will work for limiting. Depending on your version, this document will be 99% accurate and if you follow every step it will help, at least in my experience with SSRS.
Went ahead and configured the limits on it to be a little more open. With the default limits it had leveled out with about 20% of the RAM left on the server which was more than ok.
