How can I tune a portlet for optimized performance in Clarity?

Document ID : KB000031635
Last Modified Date : 15/02/2019
Show Technical Document Details

What are recommendations to help prevent performance issues in Clarity PPM in portlets/pages?

One scenario this may help with is 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 planning portlets, the general home page of Clarity, etc. 
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.
                   o   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.
         o   Be sure the row is removed, and not just hidden, as the row will still calculate if it’s configured and not marked “Show”
                    o   Each row causes additional calculations which can slow down the portlet
5.     Limit the amount of columns configured in the portlet.
        o   Recommended amount of columns returned to be limited to 10-15.
6.        Limit the amount of porttets on pages/tabs in Clarity.
7.        See the following KB KB000127139 for additional known causes of slow performance on Resource Planning portlets