You can configure Search caching through the /atg/search/routing/CacheService component. Key properties are:
defaultMaxElementsOnDisk- Set this property to a large number to avoid spending unnecessary resources purging the cache.defaultMemoryStoreEvictionPolicy- Least Recently Used (LRU) is the default. Other supported values are:FIFO(First In First Out) andLFU(Least Frequently Used).
When the configured memory amount for the cache is exceeded, the least recently used items are moved to disk; if the cache uses memory only, they are evicted.
Note that if you are using on-disk storage, the cache may eventually take up significant space on the disk, on the order of 20 GB for 800,000 cached queries. If you want to use caching but do not have enough space, you can do one of the following:
Put the cache files on a different disk. To do this, create an
/atg/search/routing/CacheService.propertiesfile and set thedefaultCacheDirectoryRootas shown.For Unix:
defaultCacheDirectoryRoot=/mnt/target_disk_nameFor Windows, where F: is an example drive:
defaultCacheDirectoryRoot=F:\\target_directoryCache only certain types of queries; set the
cacheableproperty ofSearchRequestobjects you do not want to cache tofalse, as mentioned above.
ATG does not recommend that you set limits on the size of the disk cache, as this requires the caching mechanism to spend a significant amount of resources expiring items. Instead, you should either use in-memory caching or one of the methods outlined above.
