About the different Guidewire profilers

There are multiple types of Guidewire profilers, including:
  • A Web (UI) profiler
  • Multiple entry-point profilers of various types
  • A database upgrade profiler

You use the Server Tools Guidewire Profiler > Configuration screen to configure profiler operation. Use the Configuration to select the specific type of profiler to execute, and the circumstances under which to execute the profiler. The one exception is the Upgrade profiler, which you do not have to configure as it collects data automatically during an application upgrade.

Differences between profilers

The following list describes some of the main differences between web and entry-point profilers.
Web profiler Entry-point profiler
Captures the current user session in which you enabled the profiler for a single node in the PolicyCenter cluster until you disable the profiling session. Captures all instances of targeted components across all nodes in the PolicyCenter cluster for each profiler run.
Provides a set of results for all round-trips to the server (browser-server-browser) while the profiler is active, for a single node in the PolicyCenter cluster. Provides a separate result for each individual profiler run on each node in the PolicyCenter cluster. This information includes a separate result for each instance of the profiled action, for example:
  • Each individual run of the profiled batch process
  • Each processing cycle of every profiled work item
  • Each call to the profiled web service operation
Saves profiler information in the current user session in memory so that the data disappears at session termination. Stores profiler information in the database until deleted.