Databases Reference
In-Depth Information
Figure 7-8.
Enabling caching in a page
5.
Run your form now. If you use the Monitor Activity tool to check the weighted
performance for the page, you should observe that the amount of time elapsed
in rendering the page is smaller on consecutive runs.
How It Works
Caching works not only at the region level but also at the page level. Page caching is different from
region caching in that it caches the static HTML of the entire page. If your objective for the page is to
simply display some static information that rarely changes, it is a good candidate for page caching.
The Cache By User setting allows the page to be cached by user, as opposed to caching by session.
The difference is that if you cache a page by session, all other users will use the same copy from the
cache, whereas if you cached a page by user, the data is only retrieved from the cache if it was accessed
by the same user that first accessed the page.
Tip
One problem with page caching is that sometimes the data for a cached page might have changed, and
APEX is still retrieving the cached copy. In such cases, it might be fruitful to invalidate the cache based on a
certain event. You can use the
APEX_UTIL.CLEAR_PAGE_CACHE(page_number);
function to invalidate the cache
when the user logs out of the application or after a period of inactivity, for example.
