Web (UI) profiler

After you enable web profiling, PolicyCenter records all subsequent round-trips to the application server as a separate profiler stack. Thus, the profiler records information on rendering the screen, entering the screen, taking action on the screen, updating a widget on the screen, and similar types of operations. The web profiler captures only the current user session in which you enable the web profiler. Exiting the profiler removes the profiler information from memory. Logging out of the current PolicyCenter session also ends the web profiler session.

Types of web performance issues

Remember that web performance issues can be any of the following issue types.

Issue type	Example	Profiler
Operation on a single screen	Widget update on a screen or button click on the screen	Press Alt+Shift+P to open the profiler directly from the screen on which the operation occurs.
Moving between screens	Excessive time in rendering a screen	Press Alt+Shift+P to open the profiler directly on the screen before the problematic screen. In other words, start the profiler, then navigate into the problematic screen.

How to use web profiling

In profiling a PolicyCenter application screen, press Alt+Shift+P to open the profiler popup directly from within Guidewire PolicyCenter. In setting up the profile test scenario, remember the following:

Enable Guidewire Profiler right before the screen click that you are trying to profile.
Disable the web profiler immediately after the screen click.

Specifically, you want to capture each separate screen click as a unique profiling operation so that you can analyze each profiling run separately.