IBM Support

BiLog: Performance Enablers….Traffic…and Optimizing Complex Report Processing

Technical Blog Post


BiLog: Performance Enablers….Traffic…and Optimizing Complex Report Processing


Do you ever find yourself stuck in car or airline traffic?  If you have, do you find yourself deeply sighing or groaning in agony thinking of where you need to be?  Or do you become a pounder – pounding your fists on the steering wheel or your feet thru the airline concourse while a number of choice words come muttering out of your mouth? 

Living in the Boston Area for the last 12 years, I’ve encountered a number of car and airline traffic jams.  My most recent traffic jam was last night when thunderstorms in the North East backed up air traffic for a flight delay of over 15 hours.   My car traffic delays usually aren’t that  bad....but if I’m running late and enter the highway during peak business travel commute time can be almost twice as long as if I hit the highway during non-peak travel hours when my ride is fast and efficient.

Report processing can be like traffic.  If you execute reports during peak business hours, when there is tremendous load on the application and database servers, reports can creep along slowly.  This is especially true of large, batch reports. 


However, if you execute these same reports at off-peak business hours, when the load on the servers is significantly less, these batch reports can execute much more efficiently. 


In the Maximo Version 7 releases, you can specify when your users can execute your large, batch reports.  This will prevent users from executing complex report jobs during peak times of server use.    For example, you may not want your users to run very complex batch reports against very large record sets on Monday morning, when the load on the servers are very high with users executing queries and transactional reports.  


To enable this functionality, your report administrator can define the busy days and times within a week that the specific report should not execute.  This is called ‘Reserved Processing Time’, and it is the peak processing times of the server which you also do not want to use for complex, batch report processing.   You can vary these times for individual reports, due to the wide range of report complexity you have.    


When your report users go to execute these large batch reports, they will see the days and times of the week that the report can be scheduled for execution on the report’s request page.  These times are the Schedule Availability for the individual report – which is the non-peak processing times of the server.    


Optimizing your reports for peak performance by defining when they can enter the ‘server traffic’ is just one report performance enabler you can configure.   For additional information on this or other performance enablers, see other BiLog Reporting entries located here, or the Maximo Report Wiki Pages here



[{"Business Unit":{"code":"BU005","label":"IoT"}, "Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]