How to set the number of CPU cores used by TIBCO Spotfire Statistics Services
Article ID: KB0072488
Updated On:
| Products | Versions |
|---|---|
| Spotfire Statistics Services | All |
Description
This article describes how to limit the number of CPU cores used by TIBCO Spotfire Statistics Services.
Issue/Introduction
This article describes how to limit the number of CPU cores used by TIBCO Spotfire Statistics Services.
Environment
All
Resolution
You can specify the number of CPU cores used by TIBCO Spotfire Statistics Services (TSSS), by configuring a service property for TSSS.
(a) For a standalone TSSS Service installation, by default, it will use all the CPU cores available in the server to execute jobs.
For an installation on Windows OS, you can use procrun to specify the engine count for TSSS service, as documented in
https://docs.tibco.com/pub/sf_statsvcs/11.4.5/doc/html/TIB_sf_statsvcs_11.4.5_installation/installation/topics/using_procrun_to_modify_a_java_property.html
(b) For a Cluster installation of TSSS service, TSSS service on the manager node by default will not execute jobs itself (engine count is set as 0), and the engine count for the worker node is set to the number of cores in the server by default.
For manager node on Windows OS: Go to directory SPSERVER_Home/tomcat/bin/, Run TSSS<service_name>w.exe as Administrator and add the Java Option: -Dengine.count=4
For worker node on Windows OS: Go to directory SPSERVER_Home/worker/bin/, Run TSSS<service_name>w.exe as Administrator and add the Java Option: -Dengine.count=4
For manager node on Unix/Linux OS: Go to directory SPSERVER_Home/init.d, edit file "spserver", specify SPSERVER_ENGINES=4
For worker node on Unix/Linux OS, Go to directory SPSERVER_Home/init.d, edit file "spserver", specify SPSERVER_ENGINES=4
Restart TSSS Service for the change to take effect.
(a) For a standalone TSSS Service installation, by default, it will use all the CPU cores available in the server to execute jobs.
For an installation on Windows OS, you can use procrun to specify the engine count for TSSS service, as documented in
https://docs.tibco.com/pub/sf_statsvcs/11.4.5/doc/html/TIB_sf_statsvcs_11.4.5_installation/installation/topics/using_procrun_to_modify_a_java_property.html
- Go to directory SPSERVER_HOME/tomcat/bin/,
- Run TSSS<service_name>w.exe as Administrator
- add the Java Option, for example, -Dengine.count=4
(b) For a Cluster installation of TSSS service, TSSS service on the manager node by default will not execute jobs itself (engine count is set as 0), and the engine count for the worker node is set to the number of cores in the server by default.
For manager node on Windows OS: Go to directory SPSERVER_Home/tomcat/bin/, Run TSSS<service_name>w.exe as Administrator and add the Java Option: -Dengine.count=4
For worker node on Windows OS: Go to directory SPSERVER_Home/worker/bin/, Run TSSS<service_name>w.exe as Administrator and add the Java Option: -Dengine.count=4
For manager node on Unix/Linux OS: Go to directory SPSERVER_Home/init.d, edit file "spserver", specify SPSERVER_ENGINES=4
For worker node on Unix/Linux OS, Go to directory SPSERVER_Home/init.d, edit file "spserver", specify SPSERVER_ENGINES=4
Restart TSSS Service for the change to take effect.
Additional Information
- Use procrun to specify the engine count for TSSS service
- Monitor the TSSS Service
Feedback
Yes
No
Powered by
