Rule profiling is a collection of insight features that assists the user with rule specific error debugging and performance issues. These features enable a user to be aware of what is occurring within their Specifications.
When the Rule Profiler is active it will log every event that occurs for Specifications.
It's worth noting that having the Profiler open can negatively impact performance.
This is a DriveWorks Administrator feature only and can be found in the Specification Explorer view.
There are aspects in DriveWorks such as Documents, Specification Tasks, and Model Release activity that can be difficult to track and analyze. There can also be performance issues with Specifications that are not easy to identify or solve.
Rule profiling provides a solution to these issues.
It also presents you with comprehensive details of what is happening when a Specification is running.
Clicking will put the Profiler into a new window. Clicking will return the Profiler back inside DriveWorks Administrator.
The Copy Log button will copy the Profiler Log to your clipboard.
The Clear Log button will clear the Profiler Log.
To activate the Rule Profiler:
There are three main sections in the Rule Profiler:
This provides a chronological log of events that occur in DriveWorks.
There are two main types of events:
Each value based event displays the new value that was set.
The typical pattern that can be seen in this view is a value being set and consequently a series of calculations being made. It’s useful to know what certain values are dependent on and whether they are being correctly calculated.
Performance can be summarized and adjusted by looking at the duration of each events and timpelapse display at the end of each entry.
Not everything that happens in DriveWorks is captured in this particular view. As a result there could be blank gaps displayed in the log regardless of whether time has elapsed.
Each rule based event can be double clicked to analyze the rule at the time of the event.
This displays the Functions that have been used in all Specifications while the Profiler has been open.
Function Usage is primarily used for identifying problematic Functions that could be affecting performance speed and displays potential arguments that could be causing issues.
Each function can be double clicked to view all instances of when its been used.
Similar to the Function usage section, the rule usage section displays the named rules from all Specifications.
Each rule can be double clicked to analyze the formula.
The main function Rule Usage is to provide an overview of where the "hot areas" of a Specification are. I.e. where there is a lot of usage.