The Pattern Performance page displays timing information about TPL pattern performance. TPL provides considerable power that can be used in discovering an environment. Unfortunately, some patterns are inherently inefficient or perform poorly in specific customer environments.
Determining the performance of individual patterns is extremely difficult, involving running Reasoning at debug level and then piecing together all the rules run for an individual pattern. Each pattern has performance information gathered for it by Reasoning, and this information is presented graphically on the Appliance Performance page. This makes it easier for customers and BMC Customer Support to determine which patterns are performing badly.
You can use the drop-down selector to view the pattern performance statistics for any of the last 10 days. If dates are unavailable on the selector, no log has been created for those days.
Invocation and timing information (in seconds) is displayed for each pattern and is described in the following table.
The name of the pattern.
The number of times that the pattern has been invoked in the reporting period.
|Total Execution Time||The total time spent executing the pattern|
Average Execution Time
The average execution time. This time excludes time spent waiting for discovery commands to be completed. It is the sum of the time spent running searches in the data store, updating the model, updating inference relationships, and any other work the pattern did including the execution of the pattern code itself.
Max Execution Time
The maximum amount of time taken to execute the pattern, as defined above.
Min Execution Time
The minimum amount of time taken to execute the pattern, as defined above.
Average Discovery Time
The average time this pattern has spent running discovery commands.
Average Search Time
The average time this pattern has spent performing searches on the data store.
Average Modeling Time
The average time this pattern has spent creating, updating, or deleting nodes in the model.
Average Inferencing Time
You typically view this page if you are concerned that the performance of BMC Discovery is being impacted by patterns or if you are testing a new pattern that you have written. The key points to look for are spikes in the following:
If the pattern page highlights one or more of the problems described previously, the course of action to take depends whether the pattern is a TKU pattern or one that you have developed in-house.
TKUs are shipped each month. If a TKU pattern causes a performance spike, verify that you are using the most up-to-date TKU. If you are, report the issue to Customer Support, who will advise you about the best course of action.
If you are using a pattern that you have developed, consider the following common errors: