<oXygen/> XML Editor User Guide |
Profiling activity is linked with Debugging activity, so the first step in order to profile is to switch to debugging perspective and follow the corresponding procedure (see Working with XSLT Debugger).
Enabling/disabling the profiler is controlled by the Profiler button from the debugger control toolbar. The XSLT profiler is off by default. This option is not available during a debugger session so you should set it before starting the transformation.
Immediately after turning the profiler on two new information views are added to the current debugger information views (Invocation tree view on left side, Hotspots view on right side). Profiling data is available only when the transformation ends successfully.
![]() | Note |
---|---|
Breakpoints/step capabilities may influence the result of profiling so their usage should be restricted to minimum. |
Looking to right side (Hotspots view), you can immediately spot the time the processor spent in each instruction. As instruction usually calls other instructions the used time of the called instruction is extracted from the duration time of the caller (the hotspot only presents the inherent time of the instruction).
Looking at left side (Invocation tree view), you can examine how style instructions are processed. This result view is also named call-tree, as it represents the order of style processing. The profiling result shows the duration time for each of the style-instruction including the time needed for its called children.
In any of the above views you can use the backmapping feature in order to find the XSLT stylesheet instruction definition. Clicking on the selected item cause oXygen to highlight the XSLT stylesheet source line where the instruction is defined.
When navigating through the trees by opening instruction calls, oXygen automatically expands instructions which are only called by one other instruction themselves.
The profiling data can be saved into XML and HTML format. On any view you should right click , use the popup menu and select the corresponding choice. Basically saving HTML means saving XML and applying an XSLT stylesheet to render the report as XML.
These stylesheets are also available on distribution (see the subdirectory frameworks/profiler/
of the <oXygen/> installation directory) so you can make your own report based on the profiling raw data.
If you like to change the XSLT profiler settings you should right click on view, use the popup menu and choose the corresponding "View settings" entry.
![]() | Note |
---|---|
Precision: For Java virtual machine versions less than 1.4 we provide a time measurement in milliseconds while for greater versions (1.5) the time resolution is provided in microseconds. |
![]() | Caution |
---|---|
Profiling exhaustive transformation may run into an OutOfMemoryException due to the large amount of information being collected. If this is the case you can close unused projects when running the profiling or use high values for Java VM options -Xms and -Xmx. If this does not help you can shorten your source xml file and try again. |