DriveWorks Pro 15: Rule Profiler [send feedback...]

Rule Profiler

Rule profiling is a collection of rule specific error debugging, performance solving, insight features that allow a user to see what is happening in specifications.

While active the rule profiler will record all events from all specifications.

It's worth noting that having the profiler open can have a uniformly negative effect on performance.
This is a DriveWorks Administrator feature only and can be found in the specification explorer view.

There are parts of DriveWorks such as documents, specification tasks, and model release that can be hard to track and find problems with. There can also be performance issues with specifications that might take guess work to solve.

Rule profiling provides a solution to these problems.

It also provides more understanding and confidence in what is happening when a specification is running.

Using the Rule Profiler

To activate the Rule Profiler:

  1. In DriveWorks Administrator go to the Specification Explorer and start a new specification.
  2. Once the specification is open click the Toggle Profiler button from the command bar.

There are three main sections to the rule profiler.

  • Event Log
  • Function Usage
  • Rule Usage

Event Log

This provides a chronological log of events that happen in DriveWorks.

There are two main types of events:

  • one off rule changes (either value being set or a calculation changing a value)
  • processes that span over time and contain multiple child events.

Each value based event displays the new value that was set.

The typical pattern that can be see in this view is a value being set and then a series of calculations being made as a consequence of that action. This can be good to know what depends on certain values and to make sure that they are coming out with the right values.

Performance can be gleaned by looking at the duration of each events that is display in seconds at the end of each entry.

Not everything that happens in DriveWorks is captured in this view and as such there may be unaccounted gaps in the log where there is nothing (but time has passed).

Each rule based event can be double clicked to analyze the rule at the time of the event.

Function Usage

This displays the functions that have been used in all specifications while the profiler has been open.

This view is mainly for identifying problem functions that might be causing slow downs and arguments that might be causing functions issues.

Each function can be double clicked to see all instances in which it has been called.

Rule Usage

Similar to the function usage section, the rule usage section displays all named rules from all specifications.

Each rule can be double clicked to analyze the formula.

The main function of this view is to provide an overview where the hot areas of a specification are. I.e. where there is a lot of usage.

Table of Contents