Page tree

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

The following tables provide tuning guidelines for a BMC TrueSight Infrastructure Management Server that performs both data collection and event management.

Infrastructure Management Server heap tuning parameters

Note

The following files in this table are located in the <installation directory>\pw\pronto\conf directory. 

Parameter name

File name

Description

Recommended value

MaxHeap

pnjserver.conf

MaxHeap, in MB, allocated to the JServer process

Small: 2048
Medium: 4096
Large: 10240

MaxHeap

pnrate.conf

MaxHeap, in MB, allocated to the rate process

Small: 2048
Medium: 4096
Large: 6144

MaxHeap

pnagentcntl.conf

MaxHeap, in MB, allocated to the agent controller process

Small: 2048
Medium: 4096
Large: 7168

MaxHeap

pnagent.conf

MaxHeap, in MB, allocated to the Integration Service

Small: 1024
Medium: 2048
Large: 2048

Infrastructure Management Server additional tuning parameters

Note

The pronet.conf file in the following tables refers to the file that is located in the <installation directory>\pw\custom\conf directory. 

Parameter name

File name

Description

Recommended value

pronet.ipc.socket.recvbuffersize

pronet.conf

Sets the ingress socket cache size for the socket connection between the BMC TrueSight Infrastructure Management Server and the Integration Service

Small:
Medium: 1024000
Large:1024000


pronet.ipc.socket.sendbuffersize

pronet.conf

Sets the egress socket cache size for the socket connection between the BMC TrueSight Infrastructure Management Server and the Integration Service

Small:
Medium: 1024000
Large: 1024000

pronet.instance.taskworker.size


pronet.conf

Controls the number of threads for instance data processing

Small: 5
Medium: 10
Large: 10

pronet.api.database.statsdata.BatchSize

pronet.conf

Commits the stats data in batches

Small: 20
Medium: 20
Large: 20


pronet.api.database.statsdata.MaxBatchCommitWaitTime

pronet.conf

Inserts the scheduler wait time for batch stats data

Small: 120
Medium: 600
Large: 600


pronet.apps.agentcontroller.ngpstastdbwriter.maxmsgcachelimit

pronet.conf

Number of messages cached on the BMC TrueSight Infrastructure Management Server for the stats data

Small: 100000
Medium: 250000
Large: 250000


pronet.ngp.queue.manager.queue.size

pronet.conf

Number of messages cached on the BMC TrueSight Infrastructure Management Server

Small:
Medium:200000
Large: 200000

Database (SAP SQL Anywhere) tuning parameters

Parameter name

File name

Description

Recommended value

(Windows)
COMDefine -c

pndbsrv.conf

Initial cache size, in GB, of the Infrastructure Management Database

Small: 1
Medium: 2
Large: 3

(Solaris)
setenv dbsrvicache

startdbsrv7

Initial cache size, in MB, of the Infrastructure Management Database

Small: 1024
Medium: 2048
Large: 3072

 

Integration Service tuning parameters

Parameter name

File name

Description

Recommended value

MaxHeap

pnagent.conf

MaxHeap, in MB, allocated for the Integration Service.

Small: 1024
Medium: 2048
Large: 4096

pronet.apps.is.data.queue.size

pronet.conf

Integration Service Configuration: Number of message limit per thread.

Small: 10000
Medium: 15000
Large: 20000

Cell tuning parameters

Parameter name

File name

Description

Recommended value

Tested Value

Parameter value format

EventDBSize

<installation directory>\pw\server\etc\<cell name>mcell.conf

The number of events retained in repository

Set higher for a higher event rate.

400 K

EventDBSize=400000

EventDBKeepClosed

<installation directory>\pw\server\etc\<cell name>mcell.conf

The minimum time, in seconds, before CLOSED events are removed from the repository

Set lower if event rate is high.

1 Day

EventDBKeepClosed=1d

StateBuildSize

<installation directory>\pw\server\etc\<cell name>mcell.conf

The maximum size, in KB, of a transaction file before it is transformed into a new saved state when the state builder runs again

Set higher for a higher event rate to avoid frequent state builder runs.

50 MB

StateBuildSize=50M

Configuring the parameters automatically

You can either manually add these parameter values in the respective configuration file or let the installer insert them at the time of installation. To do this, open the command prompt using the Run as administrator option and run the installer using the following command:

install.cmd –J PERFORM_SERVER_PARAMETER_TUNING=true

When you install the BMC TrueSight Infrastructure Management Server, the installation program automatically configures the system by adding the pre-inserted values for performance tuning parameters provided in the ServerPerformanceParameters.csv file. This file contains the different value for each CPU core and RAM combination for the following parameters:

Parameter Name

Property file

MaxHeap

pnjserver.conf

MinHeap

pnjserver.conf

MaxHeap

pnrate.conf

MinHeap

pnrate.conf

MaxHeap

pnagentcntl.conf

MinHeap

pnagentcntl.conf

pronet.jserver.cachemodule.threadpool.max.size

pronet.conf

pronet.jserver.cachemodule.threadpool.min.size

pronet.conf

pronet.jserver.databasemodule.threadpool.max.size

pronet.conf

pronet.jserver.databasemodule.threadpool.min.size

pronet.conf

pronet.jserver.dbconnectionpool.maxdbconnections

pronet.conf

The installer picks the values depending on your system configuration and updates the configuration files.  Post installation, this file is located at the <installationDirectory>\pw\custom\conf folder.

You can use the Maintenance Tool - Configuration tab to re-configure the values in the following cases:

  • If you have the information for different parameters (other than mentioned in the previous table) and insert the values in this csv file. 
  • If your system configuration is modified in the future.

For more information, see Administering Infrastructure Management Maintenance Tool.

Related topics

Performance tuning recommendations for BMC Cloud Lifecycle Management

Performance tuning recommendations for event and impact management

Tuning the Infrastructure Management database for performance

Best practices and configuration guidelines for performance and scalability

11 Comments

  1.  

    1.  

  2. Please provide an update on the integration service tuning as what you list above for the default is different than the default actually in the pronet.conf file:

    Default is : pronet.apps.is.data.queue.size=10000 (not 5000)

  3. As Daric mentioned we had a confirmation from the development team that the default in the code have been 10,000 since the latest three versions. Please correct that to specify the default value is 10,000 and the low is 5,000. That as I mentioned above is confirmed by dev,

     

    1.  

    2. Hello Salvador,

      I'm in conversation with the development team to confirm the default value and also the recommended value for each environment type. Should have this in the next day or two. Will provide an update then.

      Thank you for your patience.

      1. Thanks so much for the prompt response

  4. Hello Daric and Salvador,

    After internal testing, the recommended values for the IS data queue size are 10000, 15000, and 20000 for S, M, and L environments respectively. I have updated the table accordingly.

  5. Can you tell me which mcell.conf should be updated - this is referred to in the "Cell Tuning Parameters" section.  Should it be the mcell.conf found in <installation directory>\pw\server\etc OR in <installation directory>\pw\server\etc\<cell name>?

    1. Hello Cassie,

      It is the mcell.conf in the <installation directory>\pw\server\etc\<cell name> directory. I have updated the table with this information.

  6.