Other cache settings
Page compilation caching
Sitefinity supports page compilation caching. For more information, see Tips for optimizing performance » Force pages to compile.
Page compilation caching is stored in ASP.NET temporary folder. This way, it is persistent between restarts.
Database caching
To enable database caching, click Administration » Settings » Advances » Data.
In Enable data caching, enter true or false.
This setting controls the setting of the Open Access 2nd level cache.
In single instance mode, database caching is turned on by default. As of Sitefinity 7.1, in NLB mode database caching is turned on by default, as well.
Custom widgets caching
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.
Caching and permissions
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.
Cache expiration
You set cache expiration using the caching profiles, described above. You can the assign different profiles to different pages, using the Advanced options of a page. You can also programmatically expire cache using public void CacheManager.Remove (string key) where key is the ID of the page node.