Wednesday, October 22, 2014

IBM TRIRIGA Performance Best Practices

Over the last few months I have seen an increase in performance related tickets that have come into the TRIRIGA call center.  The vast majority of those tickets were resolved by following all of the recommendations outlined in the Performance Best Practices Guide and the document can be found at:


With this entry I will discuss two of the most common items from that document the I have seen.

1. Workflow instance saving.

By Default, TRIRIGA ships with this value being set to 'Errors Only' in the TRIRIGAWEB.properties file and this is also the recommended setting for production environments.  This is a very important setting since enabling workflow instance saving can cause a tremendous amount of additional overhead from a performance perspective.  Additionally, the cleanup agent may run longer than expected or run into a normal workday if there is a significant amount of data that needs to be removed.  Keep in mind that this setting can be enabled and disabled from the TRIRIGA Admin Console without the need of a restart.

2. Production Mode

Production mode is also another way to improve performance and is also recommended to be enabled in production environments.  This setting enables data from the database to be cached in memory.

The Performance Best Practices Guide has more great information on these settings as well as additional recommendations that will provide a positive performance impact to most any environment. 

Taken from https://www.ibm.com/developerworks/community/blogs/8eeee156-f1f3-45ec-970c-53b17ccb452a/entry/tririga_performance_best_practices?lang=en

No comments:

Post a Comment