Scalability and best practices


This section describes some best practices that you can use while configuring PATROL for IBM DB2. Device configuration becomes critical when a single resource agent is configured to many devices.

Hardware recommendation

Following table lists the hardware recommendation for the tested configuration scenarios in Red Hat Enterprise Linux 7.6 x86_64 platform:

Platform

Configuration Item

Value

Red Hat Enterprise Linux 7.6 x86_64

CPU

2 CPU

RAM

16GB

Type

64-bit

Scalability and sizing best practices

The table below provides information about the tested configuration scenarios. It also provides the information on the PATROL Agent performance and the application performance with respect to CPU utilization and memory. Consider the following requirements to achieve the best performance. 

Tested configuration scenarios:

Load

Instances

Parameters

Oracle Java backend collector

OpenJDK backend collector

IBM JRE backend collector

PATROL Agent

Oracle JRE 1.8.0.171

OpenJDK 11.0.2

IBM JRE 1.8

Version: 11.3.01

Memory in MB

CPU Usage

Memory in MB

CPU Usage

Memory in MB

CPU Usage

Memory in MB

CPU Usage

Local

3519

68148

~650MB

~0.15%

~650MB

~0.10%

 -

 -

~250MB

~2%

Remote Unix

4754

65757

~1.5GB

~0.10%

~750MB

~0.10%

~350MB

~0.10%

~250MB

~2%

Warning

Note

It is recommended to create a configuration on multiple monitoring categories rather than creating a configuration with a huge number of instances for a single monitoring category. For example, configuring a policy to monitor only tablespace category which contains a huge number of tablespaces is not recommended as it might affect the monitoring performance.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL for IBM DB2 9.6