Performance Tuning - The Neverending Process
Chris K 270004Y3TR Visits (8556)
Being on the IBM TRIRIGA Support team, I have seen my share of PMRs where the customer is reporting a performance issue. The intent of this blog is provide you with sufficient information so that you can at least be ahead of the ball when it comes down to determining the root cause of your IBM TRIRIGA performance issues.
First and foremost, I need to make it clear that performance can be affected by a wide range of components. Network latency, insufficient memory or CPUs on the key servers, older Java releases either being used by the application and process servers as well as on client machines, and the list goes on. We will focus only on the application in this blog post. Other components should be addressed by the appropriate IT groups like the network support, database support, and server support teams.
Second, you should review and understand the Best Practices for System Performance. The URL below will take you to a wiki page where you can get to a copy of the PDF document. Share this guide with your IT teams as it describes some detailed information regarding tuning of those other components. Ultimately, however, your IT teams may determine that their parts of the TRIRIGA infrastructure and optimally tuned. The rest of this blog post will deal with actions TRIRIGA administrators can take to identify bottlenecks and begin the process of tuning the application.
URL to Best Practices for System Performance:
Third, as a TRIRIGA Administrator, you should review performance on a regular basis. If your installation is used heavily, your performance tuning activities may need to be done on a weekly basis. If your TRIRIGA implementation is relatively small, then you might consider performance tuning activities on a monthly, quarterly, annually or some other basis. As the title of this blog post suggests, you should not simply assume that you need to do performance tuning when you first install the product and never do it again. As the database grows, performance may degrade. The application takes steps to minimize the degradation through the daily cleanup process, but that is only a small part of the tuning. Just as your car requires periodic maintenance to perform optimally, so to does the TRIRIGA application.
Your best tool for analyzing TRIRIGA performance is the performance log. In a future post, I will provide more detail on how to analyze the performance log. For now, I will simply provide instructions on how to get the data required for further analysis. Below is a step by step process to follow for gathering performance related information.
1) Login to the Admin Console
2) Click on Platform Logging in the Managed Objects section on the left side of the screen.
3) On the right side of the screen is a list of categories that have a hierarchical structure. Scroll down to the Performance Timings category.
4) Click on the check box immediately in front of Performance Timings. This will cause all of the subcategories to be checked.
5) Scroll down to the bottom of the page and click on the Apply button.
6) At this point, performance logging is turned on and the performance.log file should appear in the TRIRIGA directory structure in the log sub-directory.
7) Perform activities that users have indicated are poorly performing. This action, along with other actions taking place at the time of the testing, will get logged to the performance.log file.
8) Once you have completed the process of recreating the performance issue, log back into the Admin Console and turn off the performance logging.
9) Perform analysis of the resulting performance.log. (The details of this will be the subject of my next blog post.)