#Tibco bw process monitor code
These elements will help you find the bottlenecks in your processes and identify areas that needs to be improved in the application code or runtime configuration to reach your performances or response times target. Using the Process and Activity statistics, that are available after enabling the Statistics Collection, you can get the total execution time for application processes and activities (with average, minimum and maximum values) and the related processing time (again average, minimum and maximum values). Using the Active Processes view you can quickly see how many processes are active at a given point in time. Overall we can conclude that in average executing the target SQL statement takes 25,5 ms. The max execution time is 20 ms and min execution time is 0 ms.įrom the total Elapsed Time 13297 ms we can calculated an average Elapsed Time of 7.5 ms.
#Tibco bw process monitor update
In the example above you can see that the JDBC Update activity as executed 1755 times, you can also see that max Elapsed Time is 82 ms and min Elapsed Time is 15 ms, also the max Execution Time is 20 ms and min Execution Time is 0 ms.įrom the total Elapsed Time 57820 ms we can calculated an average Elapsed Time of 33 ms. Note that Elapse Time and Execution Time of a given activity include the time to evaluate the conditions of the transitions starting from the activity. When Execution Time is lower than the Elapse Time the difference between Elapse Time and Execution Time (‘Elapse Time’ - ‘Execution Time’) is the time spent in waiting for replies in asynchronous activities. Statistics on activities are available in the ‘Activity view’ of the previous panel (‘ Activity view’ of the ‘Process’ tab of the ‘Application’ panel when in ‘Monitor’ mode).ĭisplaying statistics on activity executionĪs in the Process statistics view the Elapse Time is the total time taken by the execution of an activity including the time spent waiting for replies in asynchronous activities like Service Invocation or JMS Request / Reply and the Execution Time is the time taken by an activity execution within BusinessWorks. You can see also that average Elapsed Time is 544 ms, max Elapsed Time is 600 ms and min Elapsed Time is 529 ms, also the average Execution Time is 7 ms, max Execution Time is 20 ms and min Execution Time is 0 ms. In the example above you can see that the process Loader has been created 510 times and completed 509 times since the BusinessWorks engine started (which means that one instance is running). This generally covers time spent in waiting for replies in asynchronous activities or waiting for the process execution to be scheduled in the BusinessWorks engine. When Execution Time is lower than the Elapse Time the difference between Elapse Time and Execution Time (‘Elapse Time’ - ‘Execution Time’) is a wait time. The Execution Time is the time taken by activity execution within BusinessWorks. The Elapse Time is the total time taken by the execution of a given for a process this include wait for replies in asynchronous activities like Service Invocation or JMS Request / Reply. Displaying statistics on process execution
0 kommentar(er)
