Diagnosing performance problems in the presentation environment
If your presentation environment performance is not up to par, there are various ways to diagnose the problem. Configuring server-side caching (and cache synchronization) is an obvious first step to improve the performance of your presentation environment. But if you find that your performance plateaus even with caching set up, your cache size may be too small.
Configuring server-side cache object size or memory size
To verify that your server-side cache is too small, set your log.level property in logback.xml to the value DEBUG and check your log for the following messages occurring multiple times:
DEBUG LRUPolicy - LRUPolicy.processPut: maximum list size exceeded
...
DEBUG LRUPolicy - LRUPolicy.processPut: reduced list size to 20
To resolve this problem, in the configuration location of the (Session-enabled) Content Service, open the Storage Layer configuration file, cd_storage_conf.xml for editing. In the file, find the element called Policy.
This element contains one or more Param elements with Name and Value attributes. Unless you want to configure individual cache regions, you can configure cache size measured in objects or in bytes:
- To configure the number of objects, ensure the presence of a
Paramelement with its name set toSizeand its value set to the number of objects you want to cache. The default value is 128. - To configure the total cache size in bytes, ensure the presence of a
Paramelement with its name set toMemSizeand its value set to the number of Kilobytes (a number followed by the letterKor Megabytes (a number followed by the letterM) that you want to cache. The value cannot be higher than the size of the Java heap size, which is 256 Mb by default.
Check if this improves your performance by saving your changes and restarting the (Session-enabled) Content Service.