This section contains information to help you tune your 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 Presentation Server that performs both data collection and event management.
TrueSight Process name | Parameter name | File name | Description | Environment recommended value | ||
---|---|---|---|---|---|---|
POC or Demo | Medium | Large | ||||
Core process | vm.args.system.2 | <TSHOME>/conf/services/csr.conf | TrueSight core Java process | 4 GB (Xmx4g) | 12 GB (Xmx12g) | 20 GB (Xmx20g) |
Index server | vm.args.system.3 | <TSHOME>/conf/services/idxsrv.conf | Index server process for Elasticsearch | 2 GB (Xmx2g) | 6 GB (Xmx6g) | 6 GB (Xmx6g) |
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:
tssh properties set eventSchedulePeriod 12000
tssh server stop
tssh server start
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.
If your environment has an on-access virus scanner enabled, the startup and access time of the Presentation Server might increase.
Exclude the 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.
Sizing the Presentation Server for Infrastructure Management data collection
System requirements for Presentation Server
Performance benchmarks and tuning for Infrastructure Management
2 Comments
Stephane Guedon
On TSPS 10.7 fix pack 1 the vm.args.system.3 does not seems to match this documentation
Mukta Kirloskar