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 "PTP/designs/perf"
m (→Two step usage) |
|||
Line 1: | Line 1: | ||
+ | == Case Study == | ||
+ | # Create a parallel project (or use an existing one) | ||
+ | ## Specify application metadata (for performance data management) | ||
+ | # Open analysis creation wizard | ||
+ | ## Select workload characterization from the list of analysis tasks | ||
+ | ### Select performance measurement/monitoring tool | ||
+ | ### Select hardware counter set | ||
+ | # Build | ||
+ | ## Create make target (for standard make) | ||
+ | #* Application may or may not need to be recompiled/rebuilt | ||
+ | # Run | ||
+ | ## Create a launch configuration | ||
+ | ### Specify performance tool options (if desired) | ||
+ | ### Specifiy other parallel execution parameters | ||
+ | ### Select run sets (number of processors) | ||
+ | ##* Generates batch script | ||
+ | # Analyze | ||
+ | ## View data in analysis tool | ||
+ | ## Create HTML report | ||
+ | |||
+ | == Case Study #2 == | ||
+ | |||
+ | == Two step usage == | ||
+ | # Right-click project to open analysis configuration (Wizard) | ||
+ | #* This creates a ... | ||
+ | # Right-click on binary to set up analysis setting (may require rebuilding project) | ||
+ | |||
== TODO == | == TODO == | ||
Line 22: | Line 49: | ||
# Add a 'include eclipse.env' line to include variables to build for different profiling/tracing options. Have users | # Add a 'include eclipse.env' line to include variables to build for different profiling/tracing options. Have users | ||
# use the variables set in eclipse.env when writing their makefiles. | # use the variables set in eclipse.env when writing their makefiles. | ||
− | |||
− | |||
− | |||
− |
Revision as of 13:05, 12 September 2006
Contents
Case Study
- Create a parallel project (or use an existing one)
- Specify application metadata (for performance data management)
- Open analysis creation wizard
- Select workload characterization from the list of analysis tasks
- Select performance measurement/monitoring tool
- Select hardware counter set
- Select workload characterization from the list of analysis tasks
- Build
- Create make target (for standard make)
- Application may or may not need to be recompiled/rebuilt
- Run
- Create a launch configuration
- Specify performance tool options (if desired)
- Specifiy other parallel execution parameters
- Select run sets (number of processors)
- Generates batch script
- Create a launch configuration
- Analyze
- View data in analysis tool
- Create HTML report
Case Study #2
Two step usage
- Right-click project to open analysis configuration (Wizard)
- This creates a ...
- Right-click on binary to set up analysis setting (may require rebuilding project)
TODO
- TAU on update site
- System PTP Preferences (TAU location)
- User Preferences
- Project Preferences
- TAU Marker in source editor
- Analysis Perspective
- MPI tool-chain (for managed and standard make projects)
- Extension PT Project
UI designs
- Performance Analysis Perspective
- Wizards to set up instrumentation/measurement options during both builds and run phases.
- Templates to set up common multiple build experiments (ie. scaling, optimization levels etc...)
- Let the user choose the TAU makefile file when adding a TAU configuration to a eclipse project.
- Add tau run-time options to the run configuration
Standard Makefile Automation
- Add a 'include eclipse.env' line to include variables to build for different profiling/tracing options. Have users
- use the variables set in eclipse.env when writing their makefiles.