Difference between revisions of "Slicer3:Performance Analysis"
From NAMIC Wiki
m (→Sample Files) |
|||
| Line 48: | Line 48: | ||
=== Profilers for Multi-threaded Applications === | === Profilers for Multi-threaded Applications === | ||
| − | * | + | * See the pages on [[ITK_Registration_Optimization]] |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=== Runtime Instrumentation === | === Runtime Instrumentation === | ||
Revision as of 04:25, 7 January 2007
Home < Slicer3:Performance Analysis| Slicer3 |
|---|
Contents
Slicer 3 Performance Analysis
We are looking into performance analysis on the Slicer3 codebase in order to streamline execution where possible, identify parts of the program to optimize, and determine which parts of Slicer3 are using the most system resources. We are currently in the process of determining which profilers to use on the various Slicer platforms.
Tools
Statistical Profilers
- GNU gprof
- gprof is not a good profiler for our needs because it doesn't support profiling multithreaded code.
- oprofile
- Shark 4 (OSX)
Profilers for Multi-threaded Applications
- See the pages on ITK_Registration_Optimization
Runtime Instrumentation
An initial valgrind suppressions file for slicer is in subversion. It includes an example command line to run it with slicer that also uses the VTK, ITK, KWWidgets suppression files.
Targets
- DICOM reader / GDCM
- vtkITK
- ImageReslice
- ITK resampler w/ deformable transform
Sample Files
oprofile:
KCachegrind:
