We’ve been on XI 3.1 since December and decided to upgrade to SP 2 last week. When we did the upgrade (which took about 10 hours because BO tried, unsuccessfully, to work with Microsoft to develop the installer) we noticed that all 8 CPUs on our PROD server were consistently/constantly spiking to 100%. This, obviously, was causing major slowness issues for our users when they tried to do anything in BO.
After working with BO support they advised to go ahead and upgrade to SP 2.1 as it had some performance fixes in the Webi Processing Server. The upgrade to SP 2.1 seems to have resolved the issue and I wanted to let everyone know about the issue with SP 2 in case they run into the same thing. The installer for SP 2.1 is also much improved as it took less than an hour to install.
As far as I can tell the issue is with reports that have sections (which I would think most companies would be using). Here’s the SP 2.1 fix as quoted in the Fixed Issues guide: “World IReportServer uses high CPU/Memory usage when processing documents with multiple inner sections.”
My recommendation would be to skip SP 2 and go straight to SP 2.1…
So we ended up doing the following to address the CPU spikes:
Increased the RAM on our PROD box
Added three additional Webi Processing Servers within the CMC (four total) to allow RAM to be better utilized on our 32 bit OS
Disabled servers (in the CMC) that we weren’t using (Crystal, Performance Manager, etc)
Cleaned up log files (we had like 8 GB of log files out there and I was told this could potentially be causing issues)
Turned off any unnecessary tracing within BO (we were using CMC tracing for a while to monitor what was going on, which is very processor intensive)
Made timeouts consistent between all of the Web.config files in the following directory Program Files\Business Objects\BusinessObjects Enterprise 12.0\Web Content\ (we originally only changed the timeout in InfoViewApp which I’m told can cause issues when it’s not consistent amongst each area)
So after all of these changes our processor is much improved. We are still getting lsass.exe process spikes ever 15 minutes or so but these spikes are minimal. I’m told this is due to some process (within BO?) that is checking authentication periodically.
(BOB member since 2009-04-03)