Showing posts with label memory. Show all posts
Showing posts with label memory. Show all posts

Friday, March 23, 2012

ReportServerService running at 99% CPU and using 1 GB of memory

The ReportServerService is running at 99% CPU and using 1 GB of memory on
Windows Server 2003. When we restart the service or the server,
ReportServerService starts running away again. This server was working OK in
the past - this problem just recently started.
Does anyone have any idea what might cause this?
Thanks,
--
RickWhat version are you running? If you don't have SP2 installed I suggest
trying that. Otherwise, I haven't seen this reported here before. I've seen
something similar but restarting the service would clear it up but in your
case this doesn't help.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Rick" <Rick@.discussions.microsoft.com> wrote in message
news:3B5BBD8B-0683-409E-87AE-195454B66CD3@.microsoft.com...
> The ReportServerService is running at 99% CPU and using 1 GB of memory on
> Windows Server 2003. When we restart the service or the server,
> ReportServerService starts running away again. This server was working OK
> in
> the past - this problem just recently started.
> Does anyone have any idea what might cause this?
> Thanks,
> --
> Rick|||Found the problem - a subscription was trying to render a large report to
Excel, but it failed and then retried continually. I had to delete the
subscription.
--
Rick
"Rick" wrote:
> The ReportServerService is running at 99% CPU and using 1 GB of memory on
> Windows Server 2003. When we restart the service or the server,
> ReportServerService starts running away again. This server was working OK in
> the past - this problem just recently started.
> Does anyone have any idea what might cause this?
> Thanks,
> --
> Ricksql

Wednesday, March 7, 2012

ReportingServic process memory consumption

Hi in my task manager i notice that ReportingServic process has been building
up in memory consumption. Is this supposed to happen?Running reports in SQL 2k and in the future Yukon require that the entire
data set be instantiated in memory... In my opinion this is a shortcoming of
the product, since you can (and maybe will) get out of memory errors, and
IIS will reset the task.
The data must be in memory so that grouping and sorting in the report can
occur... In future versions I expect that MS will add some functionality to
allow the "plan" to become smarter to use a firehose cursor under conditions
which require no grouping or sorting outside of the database query.
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Marvin" <Marvin@.discussions.microsoft.com> wrote in message
news:AA003D3E-0B3F-4F59-9B9E-0F1C9645B115@.microsoft.com...
> Hi in my task manager i notice that ReportingServic process has been
> building
> up in memory consumption. Is this supposed to happen?|||So the dataset stays in memory? Is there a way to release it after a certain
amount of time?
"Wayne Snyder" wrote:
> Running reports in SQL 2k and in the future Yukon require that the entire
> data set be instantiated in memory... In my opinion this is a shortcoming of
> the product, since you can (and maybe will) get out of memory errors, and
> IIS will reset the task.
> The data must be in memory so that grouping and sorting in the report can
> occur... In future versions I expect that MS will add some functionality to
> allow the "plan" to become smarter to use a firehose cursor under conditions
> which require no grouping or sorting outside of the database query.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Marvin" <Marvin@.discussions.microsoft.com> wrote in message
> news:AA003D3E-0B3F-4F59-9B9E-0F1C9645B115@.microsoft.com...
> > Hi in my task manager i notice that ReportingServic process has been
> > building
> > up in memory consumption. Is this supposed to happen?
>
>