Configure distributed output cache

By default Sitefinity CMS uses an InMemory ouput cache provider. To configure Sitefinity CMS to use distributed output cache you need to select one of the supported distributed cache providers and configure the selected provider

Select the default output cache provider

Sitefinity CMS can be configured to store output cache in-memory (default) or in a distributed cache data store. This behavior is controlled by the Cache Provider property of the Sitefinity CMS Global output cache settings. It is available under Administration » Settings » Advanced » System » Output Cache Settings. The supported values for the Cache Provider property are:

  • InMemory – this is the default setting. When this value is selected Sitefinity CMS stores output cache items in the server memory
  • SQLServer – select this value to use distributed cache with SQLServer as the output cache data store 

    IMPORTANT: When using SQLServer as the Sitefinity CMS output cache data store, the expired output cache items are not removed from the specified database.

  • Redis – select this value to use distributed cache with Redis as the output cache data store
  • Memcached – select this value to use distributed cache with Memcached as the output cache data store
  • AwsDynamoDB – select this value to use distributed cache with AWS DynamoDB as the output cache data store

    NOTE: When using DynamoDB as the Sitefinity CMS output cache data store, the supported maximum size of an output cache item is 400 KB. Items larger than 400 KB will not be persisted in output cache and will be recorded in the Sitefinity CMS Error.log.  For more information see Limits in DynamoDB

Configure the cache provider

When selecting a Cache Provider value different that InMemory you are configuring Sitefinity CMS to use a centralized output cache data store. You need to configure the selected cache provider, so it can connect to the desired data store. You do that by going to Administration » Settings » Advanced » System » Output Cache Settings » CacheProviders and selecting the desired distributed cache provider settings you want to configure.

  • SqlServer Settings

    To use SQLServer as your output cache storage you specify a valid connection string pointing to your desired SQL server instance. Sitefinity CMS supports standard ADO.NET connection string format, for example: Server=myServerAddress;Database=myDataBase;User Id=myUsername; Password=myPassword;

    NOTE: If you do not specify a connection string, Sitefintiy CMS will use the default one pointing to the Sitefinity CMS database.

  • Redis Settings

    To use Redis as your output cache storage you need to specify a valid Redis connection string, for example:  yq2YLjsdlf34iwushrgesdeirkfs034jsdls493=@mydomain.redis.cache.windows.net?ssl=true 

    NOTE: If you do not specify a connection string, Sitefintiy CMS will use the one configured in  LoadBalancing Redis settings. For more information see: Configure Azure Redis cache

  • Memcached Settings

    To use Memcached as your output cache storage you need to specify a valid Memcached connection string.

  • AwsDynamoDB Settings

    To use AWS DynamoDB as your output cache storage you need to specify a valid AccessKey, SecretKey and your AWS Region.



Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.

Get started with Integration Hub | Sitefinity Cloud | Sitefinity SaaS

This free lesson teaches administrators, marketers, and other business professionals how to use the Integration hub service to create automated workflows between Sitefinity and other business systems.

Web Security for Sitefinity Administrators

This free lesson teaches administrators the basics about protecting yor Sitefinity instance and its sites from external threats. Configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.

Foundations of Sitefinity ASP.NET Core Development

The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.

Was this article helpful?