• Portlet Guide
  • Quick tutorial: deploying the portlet test suite
  • Deployment
    • What is a portlet preparation? Why do I need it?
    • Deploying through the administration user interface
    • Deploying directly through the file system
  • Using in a Jahia page
    • Portlet instances
    • Portlet roles and Jahia permissions
  • Hello world portlet
    • Requirements
    • Project structure
    • Maven project descriptor
    • Portlet Java code
    • Portlet descriptor
    • Web application descriptor
    • The Tomcat deployment descriptor
    • Building and deploying
    • Redeployment
    • Troubleshooting deployment
    • Learning more
  • Support for Bridges
  • How to share portlet objects?
    • Public Render Parameters
    • Portlet Events
    • Jahia Shared Map
      • How to share a simple object?
      • How to read a simple object?
      • How to share a bean?
  • Performance
  • Using portlets on other application servers
  • Additional resources

Performance

Portlet performance is very important, as it may often be the weakest performance link in a page. As portlets are very dynamic in nature, it is important to ensure that their rendering performance is optimal. When designing your portlet, make sure that you will never calculate data systematically on render. Also, it may be a good idea to use either the Portlet API caches or integrate your own caches to make sure you do not unnecessarily regenerate the same HTML output repeatedly.

Finally, it is always recommended to test the loading of the pages in which the portlet will be used to make sure the performance impact is minimal.