Minimizing the Performance Impact of Running Background Services

As a system administrator, you can schedule, monitor, and distribute background services across all nodes in a PPM Server cluster. You can proactively monitor application performance to identify threats and eliminate them before system-wide performance problems or instability occur.

The following subset of PPM background services can be run in parallel to optimize performance and minimize bottlenecks:

  • Request Status Export Service

  • FX Rate Update Service

  • Evaluate TM Approvers Service

  • Task Actual Rollup Service.

  • Financial Metrics Update Service

  • Staffing Profile Period Sum Update Service

  • Project Planned Value Update Service

  • Resource Pool Rollup Service

These services can be run on the same or on separate server cluster nodes on two different entities, such as projects, work plans, time sheets, and so on.

Note: For information about how you can monitor background service activity, seeBackground services monitor.

Recommendations for Running Background Services

Keep in mind that the flexible service framework that you get with a clustered server environment comes with some risk. Use the following guidelines in enabling and scheduling the background services on your instance: