Performance Issues on Resource Planning Portlet Pages

Article Id: 127139
Status: Published
Updated On: 14-02-2019 14:25
Products:
CLARITY PPM FOR ITG , Clarity PPM On Premise , CLARITY PPM FEDERAL , Clarity PPM SaaS , Clarity PPM SaaS - Application , Clarity PPM SaaS - Application , Clarity PPM On Premise
Issue/Introduction:

Here are some scenarios where slow performance issues is reported in the Clarity Resource Management portlets: 

  1. Open Resource Planning-Capacity page
  2. Open Top Down Planning page
  3. Open Allocations page
  4. New User Experience (UX) Staffing Page

Environment:

Release:
Component: ODRSM

Resolution:

  1. See the following KB KB000031635 - How can I tune a portlet for optimized performance in Clarity for recommendations on tuning portlets. The amount of data returned in the portlets, aggregation rows, amount of columns on the portlet are some factors that can increase slowness and this article provides some best practices on how to alleviate the performance. 
  2. Additionally, for the resource planning portlets access right adjustments can help improve performance (particularly if access is granted at the OBS or instance level). See KB000018443 (and if on the New User Experience (UX) staffing pages see KB000117335)
  3. If on earlier versions of Clarity PPM see the following KBs for some known defects:
  • KB000032061 - Aggregation rows on Large Portlets can cause the Application to Crash With Out of Memory Errors - Fixed in Clarity 14.3
  • KB000030751 - Performance Issue on pages of Resource portlets if Pop-ups are enabled - Fixed in Clarity 14.1
       4. If the above doesn't help:
  • On Premise customers: Have the DBA check to see if there are any slow running queries, if so, using SQL Tuning Advisor can provide recommendations to optimize performance (including rebuilding the execution plan any slow running queries can help resolve the performance issue).
  • PPM SaaS Customers: Contact Broadcom Support for assistance
    • Note: Generating a PPM Action trace while reproducing the issue can help in determining if there are any slow running queries causing the issue (see steps to enable action trace at: KB000009353)