Using the Advanced caching options, you can turn on and off output and client cache globally for the entire web application and all of its sites.
You can olso control the output and client cache using cache profiles, which you can configure in the Advanced settings of Sitefinity CMS.
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:
NOTE: By default, both cache options are enabled.
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 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:
Back To Top