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|
Environment recommended value
|Core process||vm.args.system.2||<TSHOME>/conf/services/csr.conf||TrueSight core Java process||12 GB (Xmx12g)||20 GB (Xmx20g)|
|Index server||vm.args.system.3||<TSHOME>/conf/services/idxsrv.conf||Index server process for Elasticsearch||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
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. Consult the product's documentation for additional information.
In a large deployment, optimize the following parameters to enhance the UI login and response time.
Edit the installedDirectory\conf\services\csr.conf file.
In the System properties section, increase the
vm.args.system.2=-Xmx setting by 20%.
For example, if the current setting is
vm.args.system.2=-Xmx15g, update it to
Ensure that your system has sufficient RAM to accommodate this increase in value.
Update the GC related properties section with the following changes:
vm.args.system.35=-Xmsand set it to half of the