Sitefinity supports page compilation caching. For more information, see Force pages to compile.
Page compilation caching is stored in ASP.NET temporary folder. This way, it is persistent between restarts.
If your site is configured to use output caching, custom widgets are cached with the entire page. You can disable caching page by page and you can also leverage the post-cache substitution mechanism. Sitefinity exposes a class called CacheSubstitutionWrapper and, if you wanted to inject dynamic content onto cached pages, you can take advantage of this infrastructure without hindering performance.
For more information, see For developers: Use a cache substitution widget.
By default, output cache is not invalidated on changing the page permissions.
You can change this by clicking Administration » Settings » Advanced » Pages and deselect Disable Output cache invalidation when permission is changed checkbox. We do not recommend deselecting this option, because any change of permissions will invalidate the output cache of all pages.
You can set the maximum size of the items that are cached. Items larger that the predefined size are not cached. For more information how to configure caching of items, see Administration: Configure cache profiles.
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:
Sign up for our free beginner training. Boost your credentials through advanced courses and certification. Register for Sitefinity training and certification.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important