Choosing the right output caching configuration for your Sitefinity CMS is an important architectural decision and can have an impact not only on your site’s performance and scalability, but also affect your costs.
By default, Sitefinity CMS uses the web server memory to store output cache items. This option provides the fastest possible speed for getting content from cache and delivering it to site visitors, thus delivering the best page response times. In regards to maintenance InMemory output cache storage requires no extra configuration or maintenance, as server memory is used, thus being an easier solution. Although it affects the server memory consumption footprint, InMemory output cache does not require maintaining additional cost for external cache storage.
The following table compares the advantagesof using in-memory or distributed cache:
Startup time (first node)
Web server node processes the content and stores an output cache item in its memory.
Web server node processes the content and stores an output cache item in the distributed cache.
Startup time (subsequent nodes)
New web server nodes compile and processes the content and store an output cache item in their memory. Startup time is the same as first node.
New nodes get the item from the distributed cache.
Startup time is up to 5 times faster.
Each web server node uses CPU resources to processes the content and stores an output cache item.
Only the first web server node uses CPU resources to processes the content.
Average response time (of a warmed-up site)
Fetching already cached content from the server memory is faster.
Fetching already cached content from the distributed cache storage depends on network latency.
Each web server node consumes memory to stores an output cache item.
No memory is used to store output cache items on the web server nodes. Distributed cache storage is used to store items
Output cache items are persisted in the server memory and are not available after restart.
Output cache items remain on the distributed cache storage and remain available after web server node restarts.
No extra maintenance. Server memory is used.
Distributed cache storage is an extra asset that needs to be maintained.
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