All content access is routed through this cache, all content properties and metadata are cached. Its main purpose is to reduce server round-trips when content properties are accessed. This cache takes care of all configuration automatically, only cache sizes must be configured. The bigger the size, the less communication with the Content Server is needed during the lifetime of the application.

See Section 5.5, “Configuration Property Reference” for more information about the property that configures the size of this cache: repository.heapCacheSize.