Skip to Main Content
Feature Request FR-2161
Product Area Developer Experience
Status DELIVERED

1 Voters

Improve apex page and application caching strategy, cache full html content response. Dependant tables for cache invalidation.

gabriel.diaz.arias Public · Nov 5 2021

Idea Summary
The current strategy for apex page caching is a bit confusing, as it doesn't seem to perform a full caching of the response as it tries to execute page processes etc, the page cache should be instant and not executing anything, not even authorizations already executed. It would be nice having a explanation of how exactly works.

It would be nice also having the possibility of defining page or app cache automatic invalidation based on dependant tables (last updated date). Thanks to result_cache, this verification can be done instantly for determining if the cache is still valid.

Use Case
Improve apex page and app cache performance.

Preferred Solution (Optional)

This has been delivered in Oracle APEX 2.0!

Comments

Comments

  • patrick wolf Admin OP 3.8 years ago

    If you use the page-level Server Cache attributes we are not executing any processes, … The cache is read right after page authorization which we have to execute because of security reasons.

    To handle cache invalidation you can use the Server Cache condition. From the online help:

    Specify a condition. If the condition returns TRUE, the page displays from cache. If the condition returns FALSE, the page renders dynamically and is not retrieved from cache.

  • gabriel.diaz.arias OP 3.8 years ago

    I will check this out thanks!