Performance management recommendations

The following recommendations help in improving the performance of PEM Partner Repository and PEM Partner Provisioner.

• Database connection configuration

  Database connection pool is controlled by the db_max_pool_size parameter in the Setup.cfg file. Any change from the default value of 500 might also require tuning at the database side as detailed below.

  • Oracle database - For a single PEM Partner Repository and PEM Partner Provisioner deployment, ensure to increase the processes initialization parameter for oracle from the current value by a minimum of 1040. As more instances of PEM Partner Repository and PEM Partner Provisioner are added, for each instance, an extra 500 (value for db_max_pool_size) must be added to the processes initialization parameter.
• JVM heap configuration

  Liberty Application Server - For PEM Partner Repository and PEM Partner Provisioner, it is recommended that the JVM heap setting must be started at a minimum of 4GB by configuring the servers.jvm_options parameter in the Setup.cfg file.

  For example,

  servers.jvm_options="-Xms4g -Xmx4g -verbose:sizes -Xverbosegclog:logs/verbosegc.%Y%m%d.%H%M%S.%pid.txt"

  Here, JVM options are added for setting the Min/Max heap size to 4GB (-Xms4g -Xmx4g) and verboseGC logs are configured to write to the logs folder (verbose:sizes -Xverbosegclog:logs/verbosegc.%Y%m%d.%H%M%S.%pid.txt)

  Note: The suggested performance configurations are based on internal lab tests. You must test the performance configuration settings in your test environment with appropriate load and then apply the settings in the production environment.