Performance tuning recommendations for the Presentation Server


This section contains information to help you tune your TrueSight Presentation Server environment.

The information is at the server level. If your deployment use case involves more than one server, this information applies separately to each server.

The following tables provides tuning guidelines for a TrueSight Presentation Server that performs both data collection and event management.

Presentation Server tuning parameters

TrueSight Process name 

Parameter name

 

File name

 

Example

Description

 

Environment recommended value

Medium

Large

Core process max heap

vm.args.system.2

<TSHOME>\conf\custom\csr.conf

vm.args.system.2=-Xmx26g

TrueSight core Java process

12 GB (Xmx12g)

26 GB (Xmx26g)*

Core process min heap

vm.args.system.35

<TSHOME>\conf\custom\csr.conf

vm.args.system.35=-Xms13g

TrueSight core Java process

6 GB (Xms6g)

13 GB (Xms13g)*

Index server
(Ensure that you set the same value for the Xms and Xmx settings)

vm.args.system.2

<TSHOME>\conf\custom\idxsrv.conf

vm.args.system.2=-Xms6g

Index server process for Elasticsearch

6 GB (Xms6g)

6 GB (Xms6g)

vm.args.system.3

<TSHOME>\conf\custom\idxsrv.conf

vm.args.system.3=-Xmx6g

Index server process for Elasticsearch

6 GB (Xmx6g)

6 GB (Xmx6g)

Index server process memory consumption

Depending on the TrueSight Presentation Server event retention and the rate of incoming events, the index server process may consume more RAM than what is set.

For approximately 180,000 events retained in the TrueSight Presentation Server, the index server process may require 1 GB additional RAM than the max heap setting. This is required for native memory or threads that are outside the max heap process memory.

In an environment with 700,000 events or more, the index server process may consume up to 10 GB RAM. If you observe that the index server process RAM consumption is consistently higher than what is set, add additional RAM as required.

Optimize the event synchronization

If you are on a large environment and if you encounter slightly slower response times due to the large number of events being synchronized, perform the following steps:

  1. From a command prompt, go to the <installation directory>\truesightpserver\bin directory.
  2. Run the following commands to set the eventSchedulePeriod property:
    tssh properties set eventSchedulePeriod 12000
    tssh server stop
    tssh server start
    The Presentation Server service is restarted to apply the new setting.

Note

On Linux computers, add & at the end of the tssh server start and tssh server stop commands so that the process runs in the background and you can continue to use the shell.

Disable on-access virus scanners

If your environment has an on-access virus scanner enabled, the startup and access time of the TrueSight Presentation Server might increase.

Exclude the TrueSight Presentation Server installation directory from the on-access virus scanner. The following instructions are for McAfee On-Access Scan. If you are using a different product, consult the product's documentation for additional information.

  1. Access the McAfee On-Access Scan properties.
  2. On the left pane, select Low-Risk Processes.
  3. On the Exclusions tab, select Exclusions and then Add.
  4. Browse and select the Infrastructure Management Server installation directory. For example, C:\Program Files\BMC Software\TrueSightPServer. Select the Also exclude subfolders checkbox.
  5. Select OK to exclude the installation directory from being scanned by McAfee On-Access Scan.

Related topics

Sizing-the-Presentation-Server-for-Infrastructure-Management-data-collection

System-requirements-for-Presentation-Server

Performance-benchmarks-and-tuning-for-Infrastructure-Management

 

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