Troubleshooting Steps
All the above factors can contribute to the poor performance of reports. If you are encountering report performance issues, the following checks should be made to isolate the problem. Please refer to the previous sections as appropriate.
1. Are all the reports perform badly or is it only specific reports that are performing badly?
2. If all reports are performing badly, check the following:

1. Investigate the Report Server.
• Is it heavily loaded?
• Run the report on its own, with no other users running reports. Is the performance better or the same? If better, then the load on the Report Server may be the issue.

2. Investigate the Siebel Object Manager.
• Is it heavily loaded?
• Run the report on its own with no users accessing the Object Managers. Is the performance better or the same? If better, then the load on the Object Manager may be the issue.

3. If specific reports are performing badly, check the following:
      1. Investigate how much data is being processed by the report.
                 •  Try the report with different volumes to get picture of performance.

      2. Investigate the Report Design:
                 • Check search specifications.
                 • Check sort specifications. 
                 • Are aggregate functions being used? 
                 • Is MemoryDataSorter being used?
                 • Check memory usage.

      3. Break the report down to determine where the bottleneck is. Once the constraint is identified, a course or action can be defined to correct it.

Related posts:

• Performance issues for Siebel Actuate Reports Series -1
• Performance issues for Siebel Actuate Reports Series – 4
• Performance issues for Siebel Actuate Reports Series -2
• Performance in Siebel Actuate – 5
• Performance issues for Siebel Actuate Reports Series -3
• Troubleshoot Frequently occurred Siebel Actuate Errors