Diagnosing Presentation Server performance problems
If your Presentation Server performance is not up to par, there are various ways to diagnose the problem.
- Configuring cache object size or memory size
-
Configuring caching (and cache synchronization) is an obvious first step to improve the performance of your Presentation Server. But if you find that your performance plateaus even with caching properly set up, your cache size may be too small.
To verify that this is the case, set your
log.levelproperty in logback.xml to the valueDEBUGand 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 20To resolve this problem, open the Storage Layer configuration file, cd_storage_conf.xml, used by the Content Deployer, for editing. In the file, navigate to the element Configuration\Global\ObjectCache\Policy.
This element contains one or more
Paramelements withNameandValueattributes. 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 Content Deployer.
- To configure the number of objects, ensure the presence of a