The cache warming service of Oracle ATG Web Commerce improves application performance by reloading cached SQL repository data after it has been invalidated by a deployment. Cache warming attempts to return your application’s cache to the state it was in before deployment.

Your application will cache data from SQL repositories as users request it. After the data is cached, your application can handle subsequent requests for the same data more quickly because it is available in memory and does not require a database transaction. See information about SQL repository caching in the ATG Repository Guide.

The cache warming service is enabled and configured by default. If you want to use the feature to improve application performance, you do not need to take any action. The configuration options for cache warming control behavior such as:

  • Which cached repository items will be returned to the cache

  • The order in which repository items are returned to the cache

  • How many repository items are returned to the cache in each database transaction

  • When to stop reloading cached data because too many users are accessing the application

See information about the way the cache warming service reloads cached data and how to configure it in Cache Warming Behavior.