Difference between revisions of "2014 Project Week:MRMLSceneSpeedUp"
From NAMIC Wiki
| (One intermediate revision by one other user not shown) | |||
| Line 22: | Line 22: | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
| − | * | + | * Develop a plan for measuring performance. |
| + | * Consider places where we could refactor and centralize some work that is being done redundantly by many widgets and modules (e.g. monitoring node modifications). | ||
</div> | </div> | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
| − | * | + | * Collected stats related to Slicer startup time. See http://wiki.slicer.org/slicerWiki/index.php/Documentation/Labs/StartupTimeImprovement |
Latest revision as of 16:15, 10 January 2014
Home < 2014 Project Week:MRMLSceneSpeedUp
Key Investigators
- Kitware: Jean-Christophe Fillion-Robin
- Queen's University: Andras Lasso
- Isomics: Steve Pieper
Project Description
Objective
- Identify what is the next bottle neck.
- Reduce number of observers associated with MRML nodes?
- Improve internal data structure associated with nodes ?
- Follow-up of last year work.
Approach, Plan
- Develop a plan for measuring performance.
- Consider places where we could refactor and centralize some work that is being done redundantly by many widgets and modules (e.g. monitoring node modifications).
Progress
- Collected stats related to Slicer startup time. See http://wiki.slicer.org/slicerWiki/index.php/Documentation/Labs/StartupTimeImprovement
