About web session profiling

Web session profiling records timing information for specific sections of application code on the server only. Thus, the profiler starts tracking from when the application servlet on the server first receives a HTTP POST request and stops tracking when the servlet sends back its response. During this process, the profiler tracks the timing of Guidewire application code as well as the response time of application calls to the database or to external services.

Data persistence

PolicyCenter does not persist the stacks from web requests to the database. Instead, PolicyCenter stores these stacks in the user session. Logging out of the current user session deletes the profiler data. Logging out of the PolicyCenter application also ends the user session. It is only possible to enable web profiling for the current user session.

It is possible to download and save a copy of the data for a current web profiling session using the functionality on the Web Profiler screen.

Profiler recommendations

In using web profiling, Guidewire recommends the following:

• Enable the web profiler only as absolutely needed as it can possibly degrade performance.
• Clearly identify the web UI operation that you want to profile.
• Profile only a single-click operation on an application screen in each profiler run.
• Collect data about each individual operation separately.
• Log out of the PolicyCenter application to free the memory used by the profiler after you have analyzed or downloaded the profiler data.