Portlet Factory, Version 6.1.2
Deciding which actions to cache
This topic describes some guidelines that help when deciding whether or not to cache a model action.
- Action caches are shared across all users that share a profile. Therefore, cache only results that are the same for all those users.
- Model data repositories (variables, service outputs, and so on) are not shared. Never cache an action that writes to a variable that you want to be available for another action. In general, avoid caching any actions that have important side effects.
- Try to cache the most time-consuming actions.
- Cache at the highest level you can. You will reap the biggest performance benefit by caching an entire method/action list that returns a page. When a page is cached, the actual byte stream of the returned page is cached, which results in an extra performance win.
Parent topic: Cache Control builder
Library | Support |