You control the output and client cache using cache profiles, which you can configure in the following way:
Global cache settings are applied to all pages and libraries, unless explicitly specified otherwise. You can enable or disable both caching profiles via the following checkboxes:
NOTE: By default, both cache options are enabled.
If you enable output or client cache, you need to specify the default profile for each. Output and client cache come with a predefined set of profiles.
You can create your own custom cache profile and specify its properties.
Following is a list and description of the default caching profiles.
You can click on each profile and edit its properties.
You can have only one default cache profile, which is used by default for all pages.
You can set cache profiles to individual pages or libraries. If no profile is set to a page or library, the default profile is applied. You can change the default profiles and you can globally turn on and off output and client caching, regardless of individual settings made on pages and libraries. NOTE: Sitefinity CMS does not support distributed caching and AppFabric.
You can set the maximum size of the items that are cached. Items larger that the predefined size are not cached. You do this in the cache profiles, described above. NOTE: The maximum amount of memory to be used for cache is equal to the maximum size of items cached times the number of pages.
You can set the maximum cache size for Sitefinity CMS on application pool level in IIS. This setting is useful when you have multiple sites hosted on the same server and you want to set a limit on the resource use for each site. This way, the application pool automatically resets itself when its size limit is reached.
To set this, perform the following:
Apart from the global cache settings you define in Sitefinity CMS Administration, you can set a cache profile for a specific page or library. To do so:
For libraries, you can configure both output and client cache options. For example, you can configure the cache options of the Images library. To do so:
Additionally, on library level, you can configure CDN storage support. For more information, see Use CDN storage for content libraries.
Back To Top