Skip to main content
Jump to: navigation, search


< PTP‎ | designs
Revision as of 13:05, 12 September 2006 by (Talk | contribs)

Case Study

  1. Create a parallel project (or use an existing one)
    1. Specify application metadata (for performance data management)
  2. Open analysis creation wizard
    1. Select workload characterization from the list of analysis tasks
      1. Select performance measurement/monitoring tool
      2. Select hardware counter set
  3. Build
    1. Create make target (for standard make)
    • Application may or may not need to be recompiled/rebuilt
  4. Run
    1. Create a launch configuration
      1. Specify performance tool options (if desired)
      2. Specifiy other parallel execution parameters
      3. Select run sets (number of processors)
      • Generates batch script
  5. Analyze
    1. View data in analysis tool
    2. Create HTML report

Case Study #2

Two step usage

  1. Right-click project to open analysis configuration (Wizard)
    • This creates a ...
  2. Right-click on binary to set up analysis setting (may require rebuilding project)


  1. TAU on update site
  2. System PTP Preferences (TAU location)
  3. User Preferences
  4. Project Preferences
  5. TAU Marker in source editor
  6. Analysis Perspective
  7. MPI tool-chain (for managed and standard make projects)
  8. Extension PT Project

UI designs

  1. Performance Analysis Perspective
  2. Wizards to set up instrumentation/measurement options during both builds and run phases.
  3. Templates to set up common multiple build experiments (ie. scaling, optimization levels etc...)
  4. Let the user choose the TAU makefile file when adding a TAU configuration to a eclipse project.
  5. Add tau run-time options to the run configuration

Standard Makefile Automation

  1. Add a 'include eclipse.env' line to include variables to build for different profiling/tracing options. Have users
  2. use the variables set in eclipse.env when writing their makefiles.

Back to the top