Portlet or list view performance slowness optimization in Classic - Clarity

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

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

• Experiencing worsening and excessive page load times in your environment due to a custom portlet or out of the box portlet
• This can also help with:
  • pages including the project list page
  • resource lists
  • resource planning portlets,
  • the general home page of Clarity, etc. 
• Portlets can spin for several minutes and you get an error 500

Environment

Release: All Supported Releases

Component: Clarity Studio

Resolution

Filter configurations

Set “Don’t show results until I filter” on portlets

This will improve initial load time.

Create custom default filters

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. 

Check the Attribute Value Protection (AVP)setting

Set AVP to a faster setting of: “Use only secured subpages to protect attribute values on this list” if not set already. Use this option instead of “Use display conditions and secured subpages to protect attribute values on this list” if you are not using display conditions. See AVP settings: Configure to improve performance for steps on how to configure this setting

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

Limit the number of columns configured in the portlet

The recommended amount of columns returned to be limited to 10-15. 

Limit the number of portlets on pages/tabs in Clarity

Limit the number of attributes to 100 on an object

For slowness on an object on the Administration side, it's recommended to limit the amount of attributes to 100 where possible. 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.

Review the Query / NSQL

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.