Set the value in the CacheMemory directive (or in the Cache Memory field of the Cache Settings configuration form), according to the following principles. The amount of memory set in this value is used for cache infrastructure support, including the cache index, and, if memory caching is configured, to store the contents of the cache.
For optimum performance of disk caches, a minimum cache memory value of 64 MB is recommended for cache infrastructure support, including the cache index. As the cache size increases, the cache index increases, and more cache memory is required to store the index. A cache memory value of 64 MB is large enough to provide cache infracture support and store a cache index for a disk cache of up to approximately 6.4 GB. For larger disk caches, the cache memory should be 1% of the cache size.
For memory caches, the cache memory value is the amount of memory set aside for the cache infrastructure support and the cache itself. A minimum cache memory value of 64 MB is recommended.
If too much physical memory is allocated for a memory cache, undesirable operations such as "out of memory" errors or proxy server failures can possibly occur. The value limitations for cache memory are due to the limitations of a 32-bit application. Because Caching Proxy is a 32-bit application, it can use a maximum of 2 GB of memory.
Caching Proxy allocates the memory defined by the CacheMemory directive and uses it as the cache to store objects. Additional memory must be allocated, whether it is a memory cache or a raw disk cache, for data structures for the cache, network I/O and connection buffers, session buffers, and memory for the main process and for all the threads. Furthermore, it is possible that requests from some clients might need to allocate a larger memory pool block than the default. Therefore, if the CacheMemory directive is set close to the 2-GB mark, it is possible that Caching Proxy might not have enough memory to operate, especially under high request loads.
It is recommended that the value of the CacheMemory directive be less than or equal to 1600 MB. Setting the value higher than 1600 MB interferes with the memory that Caching Proxy needs for its normal operation, and causes adverse side effects. These side effects typically include but are not limited to increased CPU usage (possibly up to 100% usage), out-of-memory errors, and sluggish performance. If an overall larger cache size is required, use cache devices or implement a shared cache configuration with RCA or ICP.
You can import and export cache contents to or from a dump file. This is useful when cache memory gets lost during restart, or when deploying the same cache for multiple proxies.
Filters can restrict what is cached by matching the form of the URL request. See Controlling what is cached for details about setting filters.
Optionally, you can configure the proxy server to cache results of query requests. By default, URLs that contain a question mark (?) are not cached. Refer to Caching query responses for details.
Another option is to cache results of servlet or JSP execution from an IBM® WebSphere® Application Server. Refer to Caching dynamically generated content for details.
Refer to Maintaining cache content for information about configuring when files in the cache expire and how obsolete files are removed.
The cache can be configured to automatically refresh the most popular files on a daily basis, before they are requested. Refer to Configuring the cache agent for automatic refreshing and preloading for information.
Under certain circumstances, using a shared cache increases the likelihood that a requested file is found in the cache. Refer to Using a shared cache for information.
Maintaining concise and accurate logs is important for managing Caching Proxy. Monitoring Caching Proxy contains information about configuring and using proxy server logs.