Config changes invalidating cache
Sitefinity exposes a class called and, if you wanted to inject dynamic content onto cached pages, you can take advantage of this infrastructure without hindering performance.
You can disable caching page by page and you can also leverage the post-cache substitution mechanism.
By default, output cache is not invalidated on changing the page permissions. We do not recommend deselecting this option, because any change of permissions will invalidate the output cache of all pages.
In addition, you cannot invalidate objects that are served by an RTMP distribution.Some comments may show the approximate amount of Java heap memory required by the cache.Some object references are shared by the caches, so the amount of memory used is not as high as the approximate value may suggest.Between these two categories is semi-dynamic content. IIS automatically caches static content (such as HTML pages, images, and style sheets), since these types of content do not change from request to request.IIS also detects changes to the files when you make updates, and IIS flushes the cache as needed.
To enable database caching, click If your site is configured to use output caching, custom widgets are cached with the entire page.