Basic profiler concepts

The following list describes basic concepts that are important to an understanding of how to configure and use Guidewire Profiler.
Concept Description More information
Guidewire Profiler Guidewire Profiler records the time spent in specific processing areas done by the application code, as well as the configured rules and PCF screens. The Guidewire Profiler screens
Web profiler The web profiler records information on rendering a PolicyCenter screen, entering the screen, taking action on the screen, and similar types of operations. Web (UI) profiler
Entry-point profilers
The profiler entry point indicates the type of application component that you select to profile, a batch process, for example. PolicyCenter provides the following entry point profilers:
  • Batch process
  • Work queue
  • Message destination
  • REST operation
  • Web service
  • Startable service
  • Gosu servlets
 Entry-point profilers
Profiler tag

A profiler tag represents a section of code that Guidewire Profiler can track and analyze. A profiler tag is an alias for a piece of code in the Guidewire application for which you want to gather performance information.

The PolicyCenter base configuration contains a number of profiler tags. However, you are free to add your own custom profiler tags in addition to the existing profiler tags.

 Profiler tags
Profiler frame

A profiler frame is the unit of measurement for a profiled section of code. Thus, one profiler frame contains details of a single invocation of the profiled section of code, such as its start and finish times, for example.

 Profiler frames
Profiler stack
A profiler stack records information about one particular instance of an application thread. Examples include the following:
  • One run of a batch process
  • One server round-trip from a PCF screen
  • One processing cycle for a (work queue) work item
 Profiler stacks