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 "Eclipse Platform UI with TPTP"
(New page: ====Usage scenarios:==== General case. # Measuring base line profiling data # Change the code somewhere # Run the profiler again # Compare the resulting profile with the baseline profile ...) |
|||
| Line 1: | Line 1: | ||
| − | + | ===Usage scenarios=== | |
| − | + | ====Most general case:==== | |
# Measuring base line profiling data | # Measuring base line profiling data | ||
# Change the code somewhere | # Change the code somewhere | ||
| Line 7: | Line 7: | ||
| − | + | ===Required features:=== | |
# Fix snapshot. | # Fix snapshot. | ||
# Application interface. API allows to manage profiling within target application. | # Application interface. API allows to manage profiling within target application. | ||
| Line 17: | Line 17: | ||
# Attaching comments to profiling results | # Attaching comments to profiling results | ||
| − | + | ===Ideal profiler=== | |
Ideal profiler (haven't seen this anywhere) would offer a complete | Ideal profiler (haven't seen this anywhere) would offer a complete | ||
solution for my optimization task. That is, it would help me organize my | solution for my optimization task. That is, it would help me organize my | ||
Revision as of 14:24, 13 November 2007
Usage scenarios
Most general case:
- Measuring base line profiling data
- Change the code somewhere
- Run the profiler again
- Compare the resulting profile with the baseline profile
Required features:
- Fix snapshot.
- Application interface. API allows to manage profiling within target application.
- Call tree with invocation counts and execution time. It is already exists
in TPTP profiler, but we should to be sure that we have that there meant.
- Reverse call tree with called methods as the roots and callers as children
- Profile data comparison. Compare snapshots of different measurements with showing changes for certain figures.
- Binding profiling results with source code changes.
- Attaching comments to profiling results
Ideal profiler
Ideal profiler (haven't seen this anywhere) would offer a complete solution for my optimization task. That is, it would help me organize my "experiments" and "measurements" in a way that makes it easy to undo changes to the code if there was not much gain. It would also show me a history of the changes and the resulting gain in each step. Being able to name the steps, or attach comments to them, would be useful.