Tuning a Portlet or List View for Optimized Performance


Article ID: 31635


Updated On:


Clarity PPM On Premise


What are recommendations to help prevent performance issues in Clarity in portlets/pages/lists? Some examples where this article can help:

  • If you are experiencing worsening and excessive page load times in your environment due to a custom portlet.
  • This can also help with out of the box portlets, pages including the project list page, resource lists, resource planning portlets, the general home page of Clarity, etc. 


Release: All Supported Releases

Component: Clarity Studio


Here are some best practices that can help fine tune portlet/page load time:

  1. Set “Don’t show results until I filter” on portlets. This will improve initial load time.
  2. End users can create their own default filters using the manage filters option, instead of using “Show all” in filtering.
    • If the portlet returns a large amount of data, setting a default filter that returns a smaller amount of results will help in optimizing performance. 
  3. Set Attribute Value Protection (AVP) to faster setting of “Use only secured subpages to protect attribute values on this list” instead of “Use display conditions and secured subpages to protect attribute values on this list”.
  4. Remove unnecessary Aggregation rows.
    • Be sure the row is removed, and not just hidden, as the row will still calculate if it’s configured and not marked “Show”
    • Each row causes additional calculations which can slow down the portlet
  5. Limit the amount of columns configured in the portlet.
    • Recommended amount of columns returned to be limited to 10-15.
  6. Limit the amount of portlets on pages/tabs in Clarity.
  7. See the following KB Performance Issues on Resource Planning Portlet Pages for additional known causes of slow performance on Resource Planning portlets
  8. For slowness on an object on the Administration side, it's recommended to limit the amount of attributes to 100 to a single custom attribute. As referenced in the Clarity PPM Studio Objects and Attributes documentation, a high number of attributes can result in performance issues and the potential failure of subsequent upgrades. Consider creating a subobject rather than assigning many custom attributes to a single object.

  9. Compare if the portlet NSQL is the same as an environment that is not having the issue. 
    Obtain the trace and run the parameterized query directly on the database to review the performance.

Additional Information

See also Slow Performance in Clarity - Best Practices / List of Known issues


1558689849618000031635_sktwi1f5rjvs16g41.jpeg get_app