Configure the View Cache

When the View service converts a document to HTML, it caches the results. If it receives a request for the same document again, it retrieves the version from the cache, rather than converting it again.

You can use an internal View cache, or you can cache documents on a memcached server instance. For details about memcached servers, refer to

You can also share a cache between multiple View services.

Configure the Internal View Cache

By default, the View service uses an internal cache, stored on disk. You can configure how this cache behaves.

Use a Memcached Server View Cache

The View service can store cache documents in a memcached server instance.


By default, the memcached program has a maximum entry size limit of 1 megabyte, so it cannot process files bigger than 1 megabyte.

Use a Shared View Cache

You can share a View cache between multiple IDOL View component. To use a shared cache, you must have a memcached server instance that each IDOL View component can access. This memcached server stores information about where to find the converted cache documents, so that each IDOL View component can retrieve them.

When you use a shared cache, the ResetCache action and automatic cache expiration are unavailable. The CacheExpirySeconds parameter specifies only how often to delete old, duplicate job files, but it does not automatically delete the newest instance of a job.