Page tree
Skip to end of metadata
Go to start of metadata

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\custom\conf directory. 

Parameter name

File name

Description

Recommended value (in bytes)

MaxHeap

pnjserver.conf

MaxHeap, in MB, allocated to the JServer process

Small: 2048
Medium: 4096
Large: 7168

MaxHeap

pnrate.conf

MaxHeap, in MB, allocated to the rate process

Small: 2048
Medium: 4096
Large: 8192

MaxHeap

pnagentcntl.conf

MaxHeap, in MB, allocated to the agent controller process

Small: 2048
Medium: 4096
Large: 8192

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

Description

Recommended value

pronet.ngp.perf.queue.manager.queue.<monitor type ID>.size

Sets the stats queue size per monitor type.
Use this parameter to make changes to your configuration based on the number of instances and polling interval of attributes for a monitor type.

Ranges from 50000 to 200000 based on the number of instances for a monitor type.

Example: For 70000 monitor instances of Windows NT services, the recommended configuration is 150000.

pronet.ipc.socket.recvbuffersize

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

Small: Default
Medium: 1024000
Large:1024000


pronet.ipc.socket.sendbuffersize

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

Small: Default
Medium: 1024000
Large: 1024000

pronet.instance.taskworker.size


Controls the number of threads for instance data processing

Small: 5
Medium: 10
Large: 25

pronet.patrolagent.ack.taskworker.sizeControls the number of threads for PATROL Agent message processing

Small: 3
Medium: 10
Large: 10

pronet.api.database.statsdata.BatchSize

Note: After installing or upgrading TrueSight Infrastructure Management, manually update the parameter to the recommended values.

Commits the stats data in batches

Small: 50
Medium: 50
Large: 50

pronet.api.database.statsdata.MaxBatchCommitWaitTime

Note: After installing or upgrading TrueSight Infrastructure Management, manually update the parameter to the recommended values.

Wait time (in seconds) to commit stats data in batches

Small: 120
Medium: 120
Large: 120


pronet.apps.agentcontroller.ngpstastdbwriter.maxmsgcachelimit

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

Small: 100000
Medium: 250000
Large: 500000


pronet.ngp.queue.manager.queue.size

Number of messages cached on the BMC TrueSight Infrastructure Management Server

Small: 50000
Medium:200000
Large: 200000

pronet.ngp.instance.max.queueDefines the number of internal task distribution message queues

Small: 5
Medium: 10
Large: 20

pronet.perfdata.taskworker.sizeControls the number of threads for metric data message processing

Small: 5
Medium: 10
Large: 20

pronet.apps.agentcontroller.dbwriter.maxmsgcachelimitSets the maximum queue size for the internal communication between Agent Controller and Rate

Small: 100000
Medium: 250000
Large: 500000

pronet.jserver.cachemodule.threadpool.max.sizeMaximum thread pool size for event processing in JServer cacheSmall: 20
Medium: 20
Large: 20
pronet.jserver.cachemodule.threadpool.min.sizeMinimum thread pool size for event processing in JServer cacheSmall: 10
Medium: 10
Large: 10
pronet.jserver.databasemodule.threadpool.max.sizeMaximum thread pool size of event CRU in JServer for databaseSmall: 20
Medium: 20
Large: 20
pronet.jserver.databasemodule.threadpool.min.sizeMinimum thread pool size of event CRU in JServer for databaseSmall: 10
Medium: 10
Large: 10
pronet.jserver.dbconnectionpool.maxdbconnectionsMaximum database connection pool size for database related operations in databaseSmall: 20
Medium: 20
Large: 20
+After installing or upgrading TrueSight Infrastructure Management, manually update the parameter to the recommended values.

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 GB, of the Infrastructure Management Database

Small: 1
Medium: 2
Large: 3

 

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

Related topics

Performance tuning recommendations for 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

5 Comments

  1.  

  2.  

    1.  

    2.  

  3.