Before the portal-84-6210 fixpack, the DDMTemplate editor UI was missing the cacheable checkbox. This issue caused each DDMTemplate that was saved into the DB to not be cached. This article provides a solution to a potential heavy performance drop casued by XML parsing and template processing each time an article is displayed.
Resolution
Portal 6.2 EE Fix pack Portal-83 and below:
To resolve this problem, apply fix pack Portal-84 or the latest version. After applying the fix pack, the formerly saved DDMTemplates should be opened, set to be cacheable and resaved. If you are unsure whether your system is affected or not, please execute the following steps:
- Connect to your DB server and execute the following query:
- SELECT * FROM DDMTemplate WHERE Cacheable=0;
If you see your custom DDMTemplates in the results then you are facing this problem.
To measure how much of a problem it can cause, just take a look at the following cache as MBean: com.liferay.portal.journalcontent.util.JournalContent
If you hit pages where caching could be done, the misses counter increases and you will see plenty of cache misses instead of hits:
With heavy load, the difference between page load times can be 50-80% faster when using this fix. In addition, remember to update the DDMTemplates to be cacheable.
Additional Information
See LPS-48693 for more information.