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.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, 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 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 Param element with its name set to Size and 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 Param element with its name set to MemSize and its value set to the number of Kilobytes (a number followed by the letter K or Megabytes (a number followed by the letter M) 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.