ContentCacheArea
property). A cache configuration can be associated with a server or with a group of servers. More specifically, a
instance can be associated with the following types of objects:
, which represents one server;
, which represents one or more servers; and
, which represents a still yet larger grouping of servers and other objects based on a geographic location. (A cache configuration can also be associated with a Domain, but typically you would not want servers in different geographical sites to use the same cache, since the cache must be local to the server to benefit server performance.) On startup, and periodically thereafter, a Content Engine server checks the
object representing itself, then the
object representing the virtual server of which it is a part, and so on, searching for the most closely associated cache configuration. Referred to as the primary cache, the first cache found becomes the cache for that server. Otherwise, in the absence of any cache configuration, the server does not use a cache.
In order for a cache area to be used, at least one server must be configured to be part of the same site as the cache.
The following tables list the members exposed by IContentCacheConfiguration.
Public Properties
Name | Description | |
---|---|---|
![]() | ContentCacheArea | The configured content cache area. This file storage area stores duplicates of the document content most frequently requested, and permits those duplicates to be accessed in lieu of the originals in order to enhance the document retrieval performance of local servers. For more information on the content cache area, see the |
![]() | MaxInMemoryElementState | The maximum number of elements for the in-memory state cache. Each in-memory element corresponds to a content element in the cache. One in-memory state cache exists per server. The state cache contains state information on content elements in the primary content cache area for a server, and can potentially improve the performance of a server by reducing the number of disk accesses the server must make to retrieve state information. For example, by storing the create date/time for a cache content element, the server can determine whether other previously retrieved information remains valid (thereby possibly avoiding the need to re-retrieve information for the content element). |