We are using Reporting Services 2008 and we upgraded our Report Server databases from MSRS 2005 in October 2009. We had seven incidents in January where the CPU jumped to 100% and remained there until the server was rebooted or the Report Server was restarted. In February, we have had seven more incidents where the CPU escalated to >80% but we proactively restarted the Report Server in order to avoid a 100% CPU condition.
Although the CPU spikes start at a time when reports are running, the CPU will remain at 80-100% even after the reports have finished and there is nothing in the "queue" (ReportServer..Event table). The first time (before we had a monitor in place), the 100% CPU condition lasted for 72 hours. Task manager shows that the ReportingServicesService.exe process is the culprit, consuming 99-100% of the CPU.
I have examined the ExecutionLogStorage for the periods when the CPU spikes occur and I have also examined the ReportServerService log files. However, at this time I have been unable to find a consistent pattern or a single report that would be causing the CPU spike.
We have some good graphs of the incidents and I have examined them looking for patterns. The spikes don't appear to always happen in the same way. For instance, sometimes the CPU goes straight to 80% while other tim
View Complete Post