We’ve had XIR2 for 3 1/2 years and have not had a problem. September 15th we went live on XIR3.1, and have had some serious performance problems. There are times the server is at 100% CPU used and Page File Usage History is at 4gig or higher. I’ve identified 5 or 6 reports that are showing up in the server Event Log after timing out. If I run that report it will immediately create a fcproc.exe process using 50% CPU. The report will eventually timeout and not complete, but will release the CPU & memory. If two of these are kicked off at the same time the server comes to a crawl until one of them times out. These reports run when there is very little usage on the system. BO Support has been of little help…
We have over 1,000 users (usually about 40-55 on at a given time). Over 1,500 reports, most of which are Deski free-hand SQL. Some Crystal or Webi. ( I know, I know about using free-hand sql instead of universe, not my decision and I’m trying hard to change the method of report writing, but I must support the way they’ve been writing reports for the past 10 years.) BO Support has had me add a second Deski server each of the Deski Cache, Job and Processing servers.
Deski Cache Server - all parameters at default settings
Deski Job Server - Maximum Concurrent Jobs => 50
(all other settings are defaults)
Deski Processing Server:
Command Line: added “-type outproc”
Idle Job Timeout: 20
Max Operations Before Re-Setting a Report Job: 10
Allow Running VBA: is checked
Idle Connection Timeout: 20
Max Concurrent Jobs: 15
Oldest On-Demand Data Given to clients: 120
Preloaded Report Jobs: 1
Both Deski Processing Servers are set with the same parameters. The server is new:
Windows 2003 Server R2 Standard Edition SP2 (32-bit)
Oracle 10.2 database
Tomcat 5.5
4 gig memory
2 processors
I seem to average about 27-34 fcproc’s at any given time. Most reports just take 1-2 CPU% and run quickly. But there seems to be at least 5-6 reports that when run take 50% cpu, timeout and never complete unless they’re run when hardly anyone is on the system. Users are complaining. Any ideas would be appreciated. Thanks.
llewis (BOB member since 2002-08-29)