Performance Tools: Difference between revisions
From Modelado Foundation
imported>JohnMC No edit summary |
imported>JohnMC No edit summary |
||
| Line 85: | Line 85: | ||
| | | | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| Current auto-tuning | | Current auto-tuning tools treat a program as a black-box. What kind of white-box performance analysis techniques do you envision would be helpful for auto-tuning application performance? | ||
| | | | ||
| | | | ||
| Line 133: | Line 109: | ||
| | | | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| What kind of visualization and presentation support for bugs do you want from | | What kind of visualization and presentation support for bugs do you want from performance tools? Do you envision any IDE integration for performance tools? | ||
| | | | ||
| | | | ||
| Line 145: | Line 121: | ||
| | | | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| | | List the performance challenges that you think the next generation programming languages and models would face? | ||
| | | | ||
| | | | ||
| Line 157: | Line 133: | ||
| | | | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| | | How do you envision using performance feedback to reduce energy or power consumption? What sort of interfaces will that require for inquiry and control? | ||
| | | | ||
| | | | ||
| Line 169: | Line 145: | ||
| | | | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
| | | How can performance tools help with resilience? | ||
| | | | ||
| | | | ||
Revision as of 23:31, April 29, 2014
| QUESTIONS | XPRESS | TG X-Stack | DEGAS | D-TEC | DynAX | X-TUNE | GVR | CORVETTE | SLEEC | PIPER |
|---|---|---|---|---|---|---|---|---|---|---|
| What performance information would an application developer need to know about software developed in your X-Stack project? | ||||||||||
| What performance information would a code developer in your project need to know about your software? | ||||||||||
| What information should a performance tool use to gather from each level in your software stack? What performance information should each level of your software stack maintain for inspection by performance tools? What sort of interfaces would a tool need to get this information? Async-signal safe function to be called by a signal handler? Registered callback? | ||||||||||
| What types of performance problems do you want tools to measure and diagnose? Insufficient parallelism? Serialization? Load-imbalance? Task dependences? | ||||||||||
| What kinds of performance problems do you foresee analyzing using post-mortem analysis? | ||||||||||
| What kinds of performance problems do you foresee analyzing using on-the-fly 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? | ||||||||||
| Current auto-tuning tools treat a program as a black-box. What kind of white-box performance analysis techniques do you envision would be helpful for auto-tuning application performance? | ||||||||||
| What is your strategy to debug a DSL and its runtime? What kind of multi-level debugging support do you want for DSLs? | ||||||||||
| What kind of visualization and presentation support for bugs do you want from performance tools? Do you envision any IDE integration for performance tools? | ||||||||||
| List the performance challenges that you think the next generation programming languages and models would face? | ||||||||||
| How do you envision using performance feedback to reduce energy or power consumption? What sort of interfaces will that require for inquiry and control? | ||||||||||
| How can performance tools help with resilience? |