About entry-point profiling

Guidewire Profiler stores the data collected by the entry-point profilers in the database. This information is visible to all PolicyCenter servers in the cluster.

After you enable a profiler entry point, the next time that PolicyCenter runs an instance of that component, it checks to see if the profiler is enabled for that component. If profiling is enabled, Guidewire Profiler records the profiling data in the form of a profiler stack. The profiler records multiple stacks if the initial thread spawns more threads and the developer profiles the spawned threads. PolicyCenter persists the data from entry-point profilers to the database, making it possible to retrieve the data for later use.

Batch process profilers

Guidewire Profiler specifically does not profile a batch process that is executing at the time of you enable the profiler. Instead, the profiler begins operation the next time that the batch process executes, whether on schedule or started manually.

Work queue and message destination profilers

In order for a change in configuration to take effect for the following components, you need to perform additional work:

Component	PolicyCenter screen	Additional steps
Work queue	Server Tools Work Queue Info screen	Stop, then restart, the selected work queue.
Message destination	PolicyCenter Administration > Monitoring > Message Queues	Suspend, then restart the selected message destination.

Any change in configuration can take some time to propagate through the cluster. Also, it can take up to the full amount of the entire cache stale time for a configuration change to become visible.

Purging profiler data

The Purge Profiler Data batch process works in conjunction with configuration parameter ProfilerDataPurgeDaysOld to determine when to purge profiler data from the database. See Purging profiler data for more information.