Posted by: Ashish Kumar | April 18, 2009

Performance issues for Siebel Actuate Reports Series -4

AshishReports Server
Physical Machine and Factories
The Reports Server has a finite capacity that depends on the specification of the physical machine. It is able to run multiple factory processes that allow reports to be processed concurrently, increasing the overall throughput of reports per minute. The number of factories dictates the number of reports that can be run concurrently. There is, however, a limit to the number of factories that can be run on a physical machine. As a general rule, the number of factory processes per CPU can be between two and four. If the Reports Server needs to process more reports due to increased users, reports, or both, you can add more CPUs allowing more factories to be defined.
For a specific recommendation on how to tune your Reports Server to achieve the best performance, please work with your Technical Account Manager.
For more information on factory processes, refer to the Siebel Bookshelf > Siebel Reports Administration Guide > Maintaining the Actuate e.Reporting Server.
Reports Not Running
The Reports Server is constantly starting and stopping factory processes that are used to generate reports. When a factory process starts, the Reports Server waits two seconds before trying to use the new factory process. If there is no response from the factory process, it waits one second before trying again. If the Reports Server machine is being used heavily, these settings may not allow enough time for the factory process to start or to reply after it has started, which causes the report to not be run. This factory process timing can be adjusted by adjusting the following two parameters:
• DelayAfterCreatingOperationProcess
• DelayBetweenContactingOperationProcess

Performance Degradation
The ability of the Reports Server to process reports also depends on carrying out regular maintenance tasks. Every time a report runs, it creates a report which is stored in the Reports Server along with notification information. Storage of these reports can build up to a point where it affects the performance of the Reports Server. For example, you may see that reports do not generate as quickly, or at all. Also, some of the functionality may seem to disappear from the Actuate Management Console (Actuate 6), or the Actuate Desktop Administrator (Actuate 5) may take an exceedingly long time to open.
Please refer to the following items on SupportWeb which describes the maintenance tasks that should be carried out:
• Technical Note 395 for information on the Actuate e.Reporting Server encyclopedia maintenance for Siebel 7.0.x and Actuate 5
• Technical Note 537 for information on the Actuate e.Reporting Server encyclopedia maintenance for Siebel Version 7.5.x and Actuate 6
Another cause of poor performance is having a large number of user folders at the root level of the encyclopedia. Siebel Systems recommends that if the number of users exceeds 1000, then the ACTRestruct utility should be run after user synchronization to ensure that only a small number of folders exist at the root level. Further information on this topic is available in Siebel Bookshelf > Reports Administration Guide > Restructuring the Report Server Encyclopedia.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: