Debugger performance considerations

To get optimal performance from the debugger, consider the following points:

Expression Evaluations

Step Performance

Step performance is affected by the number of enabled variables or expressions in the monitors and the complexity of the expression. Step performance can be improved by:

Searching for a string in Source view or Listing view

String searches can be made faster by the following:

Using the Optional Parameters entry fields on line breakpoints

Values specified for these options will significantly slow down your program, because the debugger must stop for the breakpoint and evaluate the From/To/Every clause each time. Even though you do not see the program stop, it is in fact stopping so that the debugger can evaluate the stop conditions.

If possible, an alternative is to set a conditional breakpoint by specifying an expression.

Avoid setting a large number of watches

When a watch is set, the system checks after each instruction whether the value of the watched variable or expression has changed. Setting many watches may lead to slower performance.


Feedback