Performance Tools: Difference between revisions
From Modelado Foundation
imported>JohnMC No edit summary |
imported>JohnMC No edit summary |
||
| Line 13: | Line 13: | ||
! style="width: 200;" | PIPER | ! style="width: 200;" | PIPER | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| What | |- style="vertical-align:top;" | ||
| What abstractions does your runtime stack use for parallelism? | |||
| | | | ||
| | | | ||
| Line 24: | Line 25: | ||
| | | | ||
| | | | ||
| What performance information would application developers need to know to tune codes that use your X-Stack project's software? | |||
| What would | |||
| | | | ||
| | | | ||
| Line 37: | Line 37: | ||
| | | | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| What | | What would a systems software developer need to know to tune the performance of your software stack? | ||
| | | | ||
| | | | ||
| Line 49: | Line 49: | ||
| | | | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| | | What information should a performance tool gather from each level in your software stack? | ||
| | |||
| | | | ||
| | | | ||
| Line 60: | Line 61: | ||
| | | | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| What | | What performance information can/does each level of your software stack maintain for inspection by performance tools? | ||
| | | | ||
| | | | ||
Revision as of 14:14, May 2, 2014
| QUESTIONS | XPRESS | TG X-Stack | DEGAS | D-TEC | DynAX | X-TUNE | GVR | CORVETTE | SLEEC | PIPER | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| What abstractions does your runtime stack use for parallelism? | What performance information would application developers need to know to tune codes that use your X-Stack project's software? | ||||||||||||||||||||
| What would a systems software developer need to know to tune the performance of your software stack? | |||||||||||||||||||||
| What information should a performance tool gather from each level in your software stack? | |||||||||||||||||||||
| What performance information can/does each level of your software stack maintain for inspection by performance tools? | |||||||||||||||||||||
| What information would your software stack need to maintain in order to measure per-thread or per-task, performance? Can this information be accessed safely from a signal handler? Could a performance tool register its own tasks to monitor the performance of the runtime? | |||||||||||||||||||||
| What information would your software stack need to maintain in order to measure per-thread or per-task, performance? Can this information be accessed safely from a signal handler? Could a performance tool register its own tasks to monitor the performance of various layers in your software stack? | |||||||||||||||||||||
| What kinds of performance problems do you foresee analyzing using post-mortem analysis? | |||||||||||||||||||||
| What kinds of performance problems do you foresee analyzing using runtime analysis? What interfaces will be needed to gather the necessary information? | |||||||||||||||||||||
| What control interfaces will be necessary to enable runtime adaptation based on performance measurements? | |||||||||||||||||||||
| There is a gap between the application-level and implementation-level views of programming languages and DSLs. What information should your software layers (compiler and runtime system) provide to attribute implementation-level performance measurement data to an application-level view? | |||||||||||||||||||||
| What kind of visualization and presentation support do you want from performance tools? Do you envision any IDE integration for performance tools? | |||||||||||||||||||||
| List the performance challenges that you think next generation programming languages and models will face. |