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.
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.
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.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2020 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity