Salesforce B2C Commerce 24.7 > Developing Your Site > Development Components > Templates

Content Cache

Configure caching to improve your site's overall performance and can minimize customer wait time.

Static and Page Cache
B2C Commerce uses two caches for different kinds of content, each of which can be configured and invalidated separately.
Configure the Static Content Cache
The web server caches static content assets, such as images, icons, and CSS style sheets, in two ways. The global static cache holds content shared among sites at the organization level, and site-specific static caches hold content belonging to private site libraries.
Configure the Page Cache
The web server caches HTML pages generated from ISML templates that are configured for caching. You configure page caching per site. The Time To Live (TTL) for page data is the same as the TTL for static content on the site.
Create a Page Cache Partition
All pipelines in a partition have their page caches invalidated together. As with a full page cache invalidation, the cache is gradually invalidated over 15 minutes. A pipeline can only be included in one partition. You can create a maximum of 10 partitions. Each partition can contain up to 10 pipelines. A partition can get replication tasks assigned, that if chosen for a replication process that has page cache invalidation strategy 'Invalidate Impacted Cache Partitions' selected, causes the partition to be invalidated at the end of the replication process.
Invalidate a Page Cache Partition
Invalidating a page cache partition empties the cache for each pipeline. The cache is only refreshed when the pipeline is called and the appropriate page rendered. To lessen the performance impact on the storefront, the cache is invalidated over a period of 15 minutes.
Quick Fixes or Emergency Edits of Production Content
You might occasionally need to make unplanned edits to content on the Production instance that must be live within a short period of time. You can configure page cache partitions so that it is safer and has less of an effect on site performance to make these edits and replicate them.