Actions

Performance Tools: Difference between revisions

From Modelado Foundation

imported>JohnMC
No edit summary
imported>JohnMC
No edit summary
Line 109: Line 109:
|
|
|- style="vertical-align:top;"
|- style="vertical-align:top;"
| List the performance challenges that you think the next generation programming languages and models would face?
| List the performance challenges that you think next generation programming languages and models will face.
|
|
|
|

Revision as of 23:56, 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 gather from each level in your software stack? What performance information should each level of your software stack maintain for inspection by performance tools? How would a tool get this information: register a signal handler, call an async-signal safe function from a signal handler, register a callback, call a function from a registered callback, or something else?
What types of performance problems do you want tools to measure and diagnose? CPU resource consumption? CPU utilization? Network bandwidth? Network latency? Contention for shared resources? Waste? Inefficiency? Insufficient parallelism? Serialization? Load-imbalance? Task dependences? Idleness? Data movement costs? Power or energy consumption? Failures and failure handling costs? The overhead of resilience mechanisms? I/O bandwidth consumed? I/O latency? I/O characterization
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?
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.