Difference between revisions of "AHM2013-Performance Evaluation Tools"
From NAMIC Wiki
| Line 1: | Line 1: | ||
[[AHM_2013|Back to AHM main page]] | [[AHM_2013|Back to AHM main page]] | ||
| + | ==Panel== | ||
*Jim | *Jim | ||
*Steve | *Steve | ||
*Hans | *Hans | ||
*JC | *JC | ||
| + | |||
| + | ==Background== | ||
| + | Users often (rightly) request performance improvements to improve usability. Developers often have ideas about code that they suspect is consuming the time, and begin to code. But sometimes performance bottlenecks are in unexpected places that can only be quantified with detailed performance assessment tools. These tools can also help measure the impact of code changes. | ||
| + | |||
| + | ==Topics== | ||
| + | * Performance assessment tools: survey of methods and tools across platforms | ||
| + | * Demo of the Instruments package on Mac to evaluate time usage in slicer4 | ||
Revision as of 13:03, 19 December 2012
Home < AHM2013-Performance Evaluation ToolsBack to AHM main page
Panel
- Jim
- Steve
- Hans
- JC
Background
Users often (rightly) request performance improvements to improve usability. Developers often have ideas about code that they suspect is consuming the time, and begin to code. But sometimes performance bottlenecks are in unexpected places that can only be quantified with detailed performance assessment tools. These tools can also help measure the impact of code changes.
Topics
- Performance assessment tools: survey of methods and tools across platforms
- Demo of the Instruments package on Mac to evaluate time usage in slicer4
