Best Practices for System Performance
<aside> 💡 To download a PDF copy of this TRIRIGAFEEDIA Best Practices Chapter 7: IBM TRIRIGA Tuning, click the attachment below.
</aside>
TRIRIGAFEEDIA_3.x.x_Best_Practices_07_IBM_TRIRIGA_Tuning_20210421.pdf
This section discusses settings that can be tuned to optimize your IBM TRIRIGA environment.
System properties can be used to tune performance in TRIRIGA. For more information on the system properties that can be configured, see the Installation and Implementation Guide (3.7.0).
Most system properties are maintained in the TRIRIGAWEB.properties ****file and are available dynamically in the Administrator Console. For changes in the TRIRIGAWEB.properties ****file to take effect, the application server must be restarted.
The variables and settings in TRIRIGA properties files may change from one version to the next. After completing an upgrade installation, carefully review each newly installed properties file and adjust values as appropriate for your implementation. Some key properties to consider in tuning your system are listed here with their recommended values for ideal performance. For key agent-related properties, see the following section 7.1.2 Agents.
The following key properties and values can be configured for your environment:
CLEAN_HOUR: Specifies the hour at which the Platform Maintenance Scheduler (Cleanup Agent) starts, in 24-hour time of the server.
2CLEAN_TIMEOUT: Specifies the number of minutes that the Platform Maintenance Scheduler (Cleanup Agent) is allowed to run.
120WF_INSTANCE_SAVE: Configures when workflow instances should be saved. The primary use of this feature is for debugging in a non-production environment. So, in a production environment, you should always have it set to the recommended value (ERRORS_ONLY), because of the significant load on the entire system if turned on. ERRORS_ONLY is the default and saves the tracing information only for those workflows that fail with an ERROR condition. The value of NEVER was renamed to ERRORS_ONLY, but the system accepts both values, where NEVER is equal to ERRORS_ONLY. This property can also be changed without a system restart by using the Workflow Agent Manager in the Administrator Console. For more information, see the following sections 7.1.2.e Workflow Agent and 7.4 Workflow Performance.
ERRORS_ONLYERRORS_ONLYDATA_LOAD. This new value for the WF_INSTANCE_SAVE property was added and should be used in conjunction with large data loads. It is best practice to use this value for the mass or batch loading of many records. This value bypasses and never saves any instances, which increases performance and decreases database size. This can be used in production environments as well, especially if the production environment has many workflows that error out or have Stop tasks, but there are no application developers available to correct the problems in the workflows.**WF_INSTANCE_SAVE_24HR_THRESHOLD**: Configures when workflow instances should stop being saved. When excessive workflow instances are saved, the platform will stop saving if the number of saved instances exceeds a certain threshold. This feature allows administrators to set an upper bound for how many workflow instances will be saved in a 24-hour period. This setting will prevent the Platform Maintenance Scheduler (Cleanup Agent) from being impacted by excessive workflow instance data. The default value is 1000. To override the default value, set WF_INSTANCE_SAVE_24HR_THRESHOLD=#### where #### is a positive integer, and restart the server. This must be set on each server in the environment. Do not set this value to a number larger than 10000 or the Platform Maintenance Scheduler (Cleanup Agent) will take a long time to remove the debugging records.
100010000