Profiler trace options

Individual Stacks

This option stores one stack for each work item and does not roll up the data.

Use caution with the Individual Stacks option as the amount of data that the profiler collects can become unbounded. Guidewire recommends that you use this profiler option to collect data only if there are a few items in the work queue.

Stack Trace Tracking

This option captures the Java stack trace and the PCF trace at the point at which a query executes. Use caution with this tracing option as it can be very performance intensive. See General considerations for using Guidewire Profiler for more information.

Query Optimizer Tracing

This option generates data on how the database arrived at a specific execution path.

This stack trace creates a trace file on the database server.

High Resolution Clock

This option uses the Microsoft Windows 100 nanosecond clock.

Extended Query Tracing

This option tracks the parse-execute-fetch actions of a SQL statement. If executing against an Oracle database, this tracing option also tracks any wait times associated with the SQL statement, including the cause of the wait.

This stack trace creates a trace file on the database server.

Diff DBMS Instrumentation Counters

This option captures the DBMS counters at the beginning of the profiling session. It also includes analysis of the differences in the DBMS-specific report.

DBMS Instrumentation Capture Threshold for each Action (millis)

This option generates a DBMS report if an action exceeds the threshold value set by this option. This option is only available if you first enable Diff DBMS Instrumentation Counters tracing. Click Edit Configuration and select Edit DBMS Instrumentation Capture Threshold (millis) to edit the default value of 0.