ITK Registration Optimization/2007-04-06-tcon - Revision history

Aylward: /* Julien */

2007-04-06T15:52:51Z

Julien

Aylward at 15:46, 6 April 2007

2007-04-06T15:46:08Z

Aylward: /* Performance Dashboard */

2007-04-06T14:57:41Z

Performance Dashboard

Aylward: /* Performance Dashboard */

2007-04-06T14:02:48Z

Performance Dashboard

Aylward: /* Tests */

2007-04-06T14:02:24Z

Tests

Aylward: /* Tests */

2007-04-06T14:02:03Z

Tests

Aylward at 14:00, 6 April 2007

2007-04-06T14:00:58Z

New page

= Agenda =

=== Tests ===
* Two types of tests
** Baseline: LinearInterp is useful for profiling (Profile reports in Reports subdir)
** Optimization: OptMattesMI is a self-contained test

=== Timing ===
* Priority
* Thread affinity

=== Performance Dashboard ===
* Ranking computers?
** CPU, memory, etc in dashboard
** MFlops as measured by Whetstone?
* Public submission of performance
** Logins and passwords configured in cmake
** Encryption in cmake?
* Organization of Experiments/Dashboards
** When new experiment?
* Appropriate summary statistics
** Per machine: day -vs- speed/error
** Per test: mflops -vs- speed/error
** All, day -vs- change in performance

=== Review of OptMattesMI ===
* Lessons learned
** Mutex bad
** Memory good

=== ctest suite ===
* Ideal set of tests is machine specific
** e.g., Number of threads and image size

@@ Line 51: / Line 51: @@
 # CMake knows of # of CPUs and CPU cores
 # CMake knows of memory available
 === Brad ===

← Older revision		Revision as of 15:46, 6 April 2007
Line 38:		Line 38:
	* Ideal set of tests is machine specific		* Ideal set of tests is machine specific
	** e.g., Number of threads and image size		** e.g., Number of threads and image size
		+
		+	= Tasks =
		+
		+	=== Julien ===
		+	# Work with Seb to get reports from Amber2
		+	#* Result
		+	#** Amber2 is allocated to another project - therefore work will transition to machines at SPL
		+	# Define role of experiments and batches
		+	#* Work with Seb to integrate with cmake dashboard
		+	#* New experiment = new cvs tag
		+	#* New batch = nightly (possibly only if cvs has changed)
		+	# CMake knows of # of CPUs and CPU cores
		+	# CMake knows of memory available
		+
		+	=== Brad ===
		+	# Continue to develop registration pipelines
		+	#* Commit into CVS
		+	#* Implement as ctests
		+	# Optimize the meansquareddifferenceimagetoimagemetric
		+
		+	=== Seb ===
		+	# Setup CMake Dashboard
		+	# Add md5 encryption function to CMake for BatchMake passwords
		+	# Work with Julien on BatchMake Dashboard designs
		+	# Investigate other opportunities for optimization
		+
		+	=== Stephen ===
		+	# Get Seb/Brad access to SPL machines
		+	# Continue to optimize MattesMIMetric
		+	# Determine BMDashboard table structure
		+	# Have programs switch between baseline, optimized, and both testing/reporting

@@ Line 26: / Line 26: @@
 ** <em>When new experiment?</em>
 * <em>Appropriate summary statistics</em>
-** Per machine: day -vs- speed/error
+** Per machine: batch -vs- speed/error
 ** Per test: mflops -vs- speed/error
-** All, day -vs- change in performance
+** All, batch -vs- % change in performance
 === Review of OptMattesMI ===

@@ Line 22: / Line 22: @@
 * Public submission of performance
 ** Logins and passwords configured in cmake
-** <em>Encryption in cmake?<em>
+** <em>Encryption in cmake?</em>
 * <em>Organization of Experiments/Dashboards</em>
-** <em>When new experiment?<em>
+** <em>When new experiment?</em>
 * <em>Appropriate summary statistics</em>
 ** Per machine: day -vs- speed/error

@@ Line 7: / Line 7: @@
 ** Optimization: OptMattesMI is a self-contained test
 *** Submit to dashboard
 **** non-optimized speed
 **** optimized speed

@@ Line 3: / Line 3: @@
 === Tests ===
 * Two types of tests
-** Baseline: LinearInterp is useful for profiling (Profile reports in Reports subdir)
+** Baseline: LinearInterp is useful for profiling
 ** Optimization: OptMattesMI is a self-contained test
 === Timing ===