Difference between revisions of "ENZO"

From Point
Jump to: navigation, search
Line 3: Line 3:
 
  This is a short overview to the performance result of the ENZO application. For each experiment we used these inits/param files:
 
  This is a short overview to the performance result of the ENZO application. For each experiment we used these inits/param files:
  
* [http://giusto.nic.uoregon.edu/~scottb/SingleGrid_dmonly.inits | inits]
+
* [http://giusto.nic.uoregon.edu/~scottb/SingleGrid_dmonly.inits inits]
* [http://giusto.nic.uoregon.edu/~scottb/SingleGrid_dmonly_amr.param | param]
+
* [http://giusto.nic.uoregon.edu/~scottb/SingleGrid_dmonly_amr.param param]
  
 
This is a relatively small experiment but was sufficent to generate some interesting performance results. For this study we used the TAU Performance System® to gather information about ENZO's performance, in particular we are interested in the Performance of the AMR simulation at scale. We ran these experiments on NCSA's Intel 64 Linux Cluster (Abe).
 
This is a relatively small experiment but was sufficent to generate some interesting performance results. For this study we used the TAU Performance System® to gather information about ENZO's performance, in particular we are interested in the Performance of the AMR simulation at scale. We ran these experiments on NCSA's Intel 64 Linux Cluster (Abe).

Revision as of 17:49, 15 May 2008

ENZO Performance Study Summary

This is a short overview to the performance result of the ENZO application. For each experiment we used these inits/param files:

This is a relatively small experiment but was sufficent to generate some interesting performance results. For this study we used the TAU Performance System® to gather information about ENZO's performance, in particular we are interested in the Performance of the AMR simulation at scale. We ran these experiments on NCSA's Intel 64 Linux Cluster (Abe).

TAU Measurement overhead

Here is a short table listing the run-times for various experiments and the instrumentation overhead observed. Each run was on 64 processors (8 nodes).

Run Type Runtime (seconds) Overhead %
Uninstrumented runtime 1072 NA
Trace of only MPI event 1085 4.8%
Profile of all significant events 1136 6.0%
Profile with Call-path information 1196 11.6%
Profile of each Phase of execution 1208 12.7%