AI agents: the content index is at /llms.txt. Every page is also available as Markdown — send the request header Accept: text/markdown, or append .md to the page URL.
Xperience Docs

Cookie consent

We use necessary cookies (opens in a new tab) to run our website and improve your experience while browsing. Additional cookies are only used with your consent. You may revoke your consent on the Cookies Policy (opens in a new tab) page or in your browser at any time.

Configure (opens in a new tab)
  • Documentation
    InstallationUsing the Xperience interfaceDeveloping websitesConfiguring XperienceManaging usersSecuring websitesDeploying websitesManaging website contentMultilingual websitesMacro expressionsExternal utilitiesIntegrating 3rd party systemsCustom developmentE-commerce featuresOn-line marketing featuresRelease notes - Xperience 13Xperience terminology glossary
  • Tutorial
    Using the Xperience interfaceDeveloper tutorialBusiness tutorialResource hub for marketers
  • API Examples
    ConfigurationContent managementDevelopmentE-commerceOn-line marketingSocial media
  1. Home
  2. Configuring Xperience
  3. Configuring caching

Configuring caching


Was this page helpful?

Send us feedback Go back to top

Related pages

  • Caching the results of macros
  • Community Questions & Answers (opens in a new tab)
  • Contact support (opens in a new tab)

Cache is a storage space that duplicates previously requested data, and allows faster access to the data in the future. Correctly using caching can significantly improve the performance of your website.

Caching the content of web pages provides two primary benefits:

  • Quicker loading of data (retrieving data from the cache avoids communication with slower storage spaces, such as the website's SQL database and file system)
  • Reduction of unnecessary page processing on repeated requests

The built-in caching mechanisms of Xperience work primarily on the server side, and utilize the application's memory to store data. The system saves data into the cache in the form of cache keys. Cache keys have unique names that exactly identify the cached content. Each key stores the cached data itself (depending on the type of the cache), as well as other information such as the expiration time or dependencies.

To learn about the available caching options, see Caching on MVC sites.