Site page cache settings and cache-clearing events
Key Takeaway
Every cache invalidation takes a 15-minute Clear Period to finish. A new invalidation request during that period restarts it, so repeated clears can keep the cache from ever being fully evicted and leave stale pages on the storefront.
B2C Commerce speeds up a storefront by having the web server keep copies of generated HTML pages and static files, so repeat requests skip the application server. You turn on page caching per site in Business Manager. Each ISML template then opts in with the <iscache> tag. A cached page stays until its caching time runs out, a replication runs, or someone invalidates the cache.
The page cache and the static content cache
B2C Commerce has two caches. You configure and invalidate them separately. The static content cache holds images, icons, CSS style sheets and other non-dynamic assets. The page cache holds HTML pages generated from ISML templates that use the <iscache> tag.