Administration: Global cache settings

Using the Global cache settings, you can control the behavior of your entire Sitefinity CMS web application. You can turn on and off output and client cache, specify cache storage, configure the default cache profiles for different content types, and so on.

RECOMMENDATION: We recommend that you configure and manage cache profiles in the dedicated Cache profiles Basic Settings section. For more information, see Administration: Configure cache profiles.

To configure global cache settings, navigate to Administration » Settings » Advanced »System » Output Cache Settings. 

Global cache settings are applied to all pages and libraries, unless explicitly specified otherwise. You can enable or disable both caching types using the following checkboxes:

• Enable Output Cache
  Controls the page output cache. If you disable output cache from this setting, no pages are cached regardless of the programmatic or declarative settings.
• Enable Client Cache
  Controls whether client cache is globally enabled. If you disable client cache, no resources are cached on the client browser.

NOTE: By default, both cache options are enabled.

This setting enables you to specify  whether Sitefinity CMS should store output cache in-memory (default value) or in a distributed cache data store. For more information about configuring distributed cache see: Configure distributed output cache.

The Global cache settings screen enables administrators to configure the default profiles used for pages and media content types in the system. The available settings are:

• Default Output Cache Profile
  This property lets you determine the default output cache profile that applies to all pages in your Sitefinity CMS web application. To change this setting, type the name of the Page Cache Profile you want to make default. To see a list of the available page cache profiles in your Sitefinity CMS and inspect their settings, navigate to Administration » Settings » Advanced »System » Output Cache Settings » Page Cache Profiles.
• Default cache profile for image libraries
  This property lets you determine the default  cache profile that applies to all images in your Sitefinity CMS web application. To change this setting, type the name of the Media Cache Profile you want to make default. To see a list of the available media cache profiles in your Sitefinity CMS and inspect their settings, navigate to Administration » Settings » Advanced »System » Output Cache Settings » Media Cache Profiles.
• Default cache profile for document libraries
  This property lets you determine the default  cache profile that applies to all documents in your Sitefinity CMS web application. To change this setting, type the name of the Media Cache Profile you want to make default. To see a list of the available media cache profiles in your Sitefinity CMS and inspect their settings, navigate to Administration » Settings » Advanced »System » Output Cache Settings » Media Cache Profiles.
• Default cache profile for video libraries
  This property lets you determine the default  cache profile that applies to all videos in your Sitefinity CMS web application. To change this setting, type the name of the Media Cache Profile you want to make default. To see a list of the available media cache profiles in your Sitefinity CMS and inspect their settings, navigate to Administration » Settings » Advanced »System » Output Cache Settings » Media Cache Profiles.

This property specifies the maximum amount of time, relative to the time of the request, a static resource (for example JavaScript) will be considered fresh by browser clients. The Client Max Age setting determines the value of the the max-age directive that Sitefinity CMS sets for the Cache-Control response header. The value must be specified in seconds.

This option indicates whether page should be served only once before its output cache is filled - when a page is requested for the first time. Afterwards, it is locked for further requests until its content is stored in the output cache. Every other request will get the page from the output cache. In this way, extensive database and CPU loads are avoided on application start or on publish of a template.

By default, this option is turned off. This way, one page can be served and compiled more than once before it enters output cache. Every request which is made toward that page before it enters into the output cache, will get the page from database and recompile it. On a website with big load, this behavior might cause slower application startups or slowdowns after publishing a page template.

NOTE: Sitefinity CMS does not support AppFabric.