How did we improve lease and platform performance?


Improvements in IBM TRIRIGA Performance

By Rick Rhea & Jay Manaloto

What has the IBM TRIRIGA performance team been up to? Over the last few years and last few releases, our performance team has focused on areas that aren’t normally covered by our standard benchmark tests, and on tools that can help customers to resolve performance issues on their own. If you’re interested, here are a few of our recent improvements in lease and platform performance.

  • Lease Benchmark Testing: Not only are database server and process server resources especially important, but using multiple process servers improves performance.
  • New Recommended Indexes: Several additional indexes were identified and added to the best practices to obtain the best response times and resource utilization of the database server.
  • Lease Journal Entries: By redesigning journal entry processing with parallel and batch processing, and multiple process servers, our test results took only about 2.5 hours instead of over 90 hours.
  • Platform Enhancements: Dynamic workflows can now pass and return parameters, the Query task can now return the number of records instead of the actual records, and the Trigger Action task can now run the asynchronous event that occurs after the transition by a user other than the currently logged-in user.
  • BIRT Reporting & Lease Disclosure Reports: In Version 3.6.1, the reporting was modified to improve running on a separate BIRT server, and to avoid the problematic “params.displayText”.
  • Performance Analyzer Tool: In Version 3.5.3, this tool was introduced to allow a customer to run specific logging types without using the Admin Console, and to view easy-to-read reports.
  • Module Level Associations, Early Adopter Feature: In Version 3.7.0, the platform was enhanced to support Module Level Associations (MLA) tables where the records in the IBS_SPEC_ASSIGNMENTS table are distributed into smaller tables that are created by module type.

By applying the above finding and tools, our recent IBM TRIRIGA 10.7.0 / 3.7.0 release has demonstrated a significant improvement in performance over previous releases. But we’re not done yet! Our performance team will continue to dig deeper into weaker areas or potential opportunities to make our products stronger or faster. So stay tuned for any upcoming developments!

Note: For future releases, “Module Level Assignments” will be renamed “Module Level Associations”.

References:

[Admin: This post is related to the 07.27.17 post about the Performance Analyzer. To see other related posts, use the Performance tag.]

Continue reading

IV93595: Workflows in selecting a work resource is not optimized


Go to Tasks > Manage Work Tasks > Work Task. Click Add for a new work task. Create the draft. Go to the Resources tab, and click Find Organization. Select Organization and click OK. The Resources page takes 6-8 seconds for it to refresh and be available to the user for further action.

This process is a synchronous process. The time it can take to perform the action can vary based on the number of records being selected.

[Admin: A similar article is posted in the IBM Support Portal about slow performance when selecting an organizational resource for a work task. This post is related to the 02.01.17 post about a long-running workflow that hangs the form, and the 02.06.17 post about the TRIRIGA Workflow Analysis Utility. To see other related posts, use the Synchronous tag or Performance tag.]

Continue reading

Where can you find the IBM TRIRIGA Workflow Analysis Utility?


The IBM TRIRIGA Workflow Analysis Utility analyzes workflow performance and process execution. The utility reads IBM TRIRIGA performance logs and displays performance analytics for workflows, including workflow execution time, and process flow (the order in which workflows ran and what triggered them to run).

Download and unzip the WorkflowAnalysisUtility.zip file. Included in the ZIP file is a WFAnalysisUtility.pdf file that contains instructions on how to use the utility. The utility does not require installation, but some configuration might be necessary to get it to run in your environment.

The utility has been updated to use Java 8.

[Admin: This post is related to the 05.27.16 post about the Workflow Agent slowing down, and the 03.13.15 post about an issue with the utility.]

Continue reading