Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Execution Analysis"
(→Execution Analysis : Identify a bottleneck) |
(→Compressed mode) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 11: | Line 11: | ||
Once a potential bottleneck is identified, '''Open Source''' action in context menu is a quick way to navigate to the source code for further investigation of problem. | Once a potential bottleneck is identified, '''Open Source''' action in context menu is a quick way to navigate to the source code for further investigation of problem. | ||
::[[Image:Snap21.jpg]] | ::[[Image:Snap21.jpg]] | ||
| + | |||
| + | == Compressed mode == | ||
| + | Execution Analysis contains an option that allow the collection of profiling data in compressed mode, aka aggregated mode. | ||
| + | Compressed mode provides a quick starting point to analysis the data if volume of data is a concern. Note that compressed mode does not provide graphical support nor call tree support. However, tabular method invocation detail is available in compressed mode selection. | ||
| + | |||
| + | Compressed mode can be enabled by selecting the option in the Execution Analysis dialog. | ||
| + | ::[[Image:Snap30.jpg]] | ||
| + | |||
------------- | ------------- | ||
| − | + | ←[[Profiling with TPTP - plug-in developmeet|Back to Profile with TPTP - plug-in development page]] | |
| + | |||
| + | ←[[TPTP|Back to TPTP wiki page]] | ||
Latest revision as of 15:49, 10 October 2008
Execution Analysis : Identify a bottleneck
Execution Statistics view provides several approaches to identify a potential bottleneck in an application run. By changing the view to Method level Information orientation, list of methods is shown in the table.
Sort the table with Base Time column, the method with most time spend will be shown as top of the list.
Further investigation can be done by opening the Method Invocation views. They shows invocation detail about the methods like the callee and caller of the method in selection.
Alternatively, Call tree tab is useful to quickly identify the bottleneck of an application run by inspecting the highest percentage of time spend in each thread of the application.
Once a potential bottleneck is identified, Open Source action in context menu is a quick way to navigate to the source code for further investigation of problem.
Compressed mode
Execution Analysis contains an option that allow the collection of profiling data in compressed mode, aka aggregated mode. Compressed mode provides a quick starting point to analysis the data if volume of data is a concern. Note that compressed mode does not provide graphical support nor call tree support. However, tabular method invocation detail is available in compressed mode selection.
Compressed mode can be enabled by selecting the option in the Execution Analysis dialog.
