CA PPM Tech Tip: How can I help tune a portlet for optimized performance in Clarity?

Discussion created by Kristin_Schroer Employee on Sep 17, 2015
Latest reply on Sep 18, 2015 by urmas

Are you thinking about creating a new portlet, or noticing some slowness in an existing portlet? If so, this tip can help you in optimizing portlet performance. We’ll go over some best practices in fine tuning portlet/page load times below:


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. Each row causes additional calculations which can slow down the portlet. Be sure the row is removed, and not just hidden, as the row will still calculate if it’s configured and not marked “Show”.


5.     Limit the amount of columns configured in the portlet. It’s recommended to limit the amount of columns returned to 10-15.


      6.  Limit the amount of portlets on pages/tabs in Clarity and put large portlets on their own pages. It’s recommended to limit the amount of portlets particularly on the general page, otherwise, this will slow down the log in process for users each time they log in.

   7.     7.     If you are on Clarity 13.3 or lower, disable pop-ups for resource portlets in Clarity, due to a known defect. See KB: Performance Issue on pages of Resource portlets if Pop-ups are enabled.

Here is a link to the knowledge base document on this topic: