Whitepapers

3 Step Process to Performance Tuning

Issue link: http://interloc.uberflip.com/i/462247

Contents of this Issue

Navigation

Page 0 of 2

Whether it's inputting a Work Order or running a BIRT report, optimal Maximo performance is your key to success. So how does the techni- cally savvy Maximo professional detect the problems, improve performance and become a Maximo super hero? In a nutshell, there are 3 basic steps: 1. Reproduce the problem 2. Identify the culprit 3. Resolve the problem Reproducing the Problem To reproduce the problem, take into account the network connection, desktop performance, Java customizations and concurrent user count, as these all play into how Maximo is performing. It is equally important that you personally verify that the action is consistently slow. Work with the local IT group onsite or remote directly into the user's workstation. If the system is live, ask the user for a detailed list of actions, fields, and applications frequently accessed. Identify the Culprit Identifying the culprit is probably the most difficult, yet most important, step of this 3-step process. You need to know what to fix before you can fix it. After all, implementing a cluster does not fix a problem with a database query. Performance issues typically fall into several key areas: client workstation, network, appli- cation and database. And because of this, it's a good thing that there are tools that can help you determine the source of the problem: • Start with the Interactive Performance Analysis with Maximo Activity Dashboard (MAD) built into Maximo to help identify the problem. • Move on to the Fiddler Web Developer Proxy or the Charles Web Developing Proxy Application from within the client's environment to track a single request from client to server. This will help to determine how much time was spent in the network versus the server. • Enable mxe.db.logSQL.Plan and mxe. db.logSQL.Timelimit to identify slow database queries. • Avoid putting logic into save() or init() methods. Certain processing may be able to move to an async process such as a crontask or escalation. • Simplify your screen. When a screen loads, it initializes the Maximo Business Object (MBO), causing all fields and tables to dis- play on the screen. Complex screens and relationships will load slow. • Simplify your logic. Embedding many, or complex, conditional expressions can slow the screen down. Consider cloning the ap- plication to provide different views. After identifying the source of problem, you'll know where the bottleneck resides and can determine the next actions to take. Along with the source, it is important to under- stand and quantify how the system will per- form when under load. Load testing lets you simulate a given user load on the system and recording the results. A load test can simulate several hundred users interacting with various applications, workflows, and interactions. Try HP Loadrunner, JMeter, or Stresstester to help determine performance under load. (For an even more detailed analysis, enable ver- bose garbage collection in Websphere and use the IBM HealthCenter.) 3-Step Process to Maximo Performance Tuning Jeremy Rempel, Principal Maximo Consutant Bottom line is... To solve the problem, you need to replicate it.

Articles in this issue

Archives of this issue

view archives of Whitepapers - 3 Step Process to Performance Tuning