System information

Using the Profiler to Troubleshoot Performance Problems
Part Number 820-2952-10 Page 157
By default, the configuration includes all your custom classes and most Identity Manager classes. A
number of Identity Manager classes are forcibly excluded — because enabling them would break
the Profiler.
For example, classes from the workflow, forms, and XPRESS engines are excluded or the Profiler
would produce an unintelligible snapshot when profiling Java and Identity Manager objects.
Note that Java filters provide much more filtering granularity than IDM Object Filters. Java
instrumentation adds significant overhead to the execution time, which can drastically skew the
profiling results. Because Identity Manager objects are interpreted rather than compiled, the
instrumentation overhead is negligible. So for example, there is basically no reason to exclude
workflow A and include workflow B, and so forth.
Miscellaneous
The Miscellaneous tab provides the following options:
Prune snapshot nodes where execution time is 0:
Disable this option (default) if you want the snapshot to include invocation information
for all executed entities — even those whose execution time is zero.
It might be useful to have the number of invocations, even for nodes where there is no
execution time.
Enable this option to remove these nodes, which allows you to focus on the most
relevant profiling data. In addition, enabling this option can provide a large savings in
Profiler snapshot size.
Automatically Open Browser Upon Profiler Start:
Enable this option (default) when you launch the Profiler to automatically open a
browser that points to the Identity Manager instance being profiled.
Disable this option if you do not want to open a browser.
Include Java Sources in Snapshot:
Enable this option (default) to include Java sources for any Java methods referenced by
the profiling data in the Snapshot. You should always use this setting for snapshots in
the field. Custom Java is relatively small and it is very valuable to have for support.
NOTE You cannot modify Java filters while the Profiler is running. You must stop the
Profiler before changing Java filters.