Changes between Version 19 and Version 20 of u/erica/ScalingBluestreak

Timestamp:

11/04/14 12:10:39 (10 years ago)

Author:

Erica Kaminski

Comment:

—

u/erica/ScalingBluestreak

@@ -3 +3 @@
 == '''Scaling on Bluestreak''' ==
 
-=== Colliding Flows Run - Hydro, Shear Angle 15 ===
 
-* Extremely poor scaling on Bluestreak
-
-* Memory errors with more nodes (remedied with different hypre library)
-
-* Delicate balance between speeding up sims with more nodes, and encountering memory issues that kill the sims (remedied with different hypre library)
-
-|| Nodes || Frames || Time to make 1 frame || Notes ||
-|| 32 || 32-39 || 3 hours || wall-time ran out ||
-|| 256 || 39-48 || 1 hours || memory died 48.4 ||
-|| 512 || 48-49 || 1 hours || memory died 49.5 ||
-|| '''32''' || '''49-50''' || '''4 hours''' || '''walltime ran out''' ||
-
-[[Image(chart_1.png)]]
-
-As the number of nodes increases, more patches are made, leading to more ghost zones. Thus, the global info as reported in standard out (that includes physical and ghost zones) increases with nodes.
-
-[[Image(chart_2.png)]]
-
-Peak goes down, as the amount of info is distributed over more and more cores.
-
-[[Image(chart_4.png)]]
-
-Percent efficiency as given in the standard out.
-
-
-[[Image(chart_3.png)]]
-
-The time to write to file increases with nodes. This can affect scaling computation (see http://astrobear.pas.rochester.edu/trac/astrobear/wiki/u/erica/ScalingBluestreak for details).
-
-The memory error is given in 2 places: 1) end of astrobear.log, and 2) a 'core' file that is written to the run directory. I am attaching as an example, the memory error reports for Shear15, nodes 256.
 
 
@@ -89 +58 @@
 The question is, which combination gets me the most frames per hour? With 3 simulations on 512 nodes, the viable options are 1) 1 job with 512 nodes, 2) 2 jobs with 256 n each, 3) 2 jobs @ 128 n, and a 3rd @ 256. Adding up the total frames per hour for the different options shows that option 3) yields the most frames per hour.
 
+== Colliding Flows Run - Hydro, Shear Angle 15 ==
+
+* Extremely poor scaling on Bluestreak
+
+* Memory errors with more nodes (remedied with different hypre library)
+
+* Delicate balance between speeding up sims with more nodes, and encountering memory issues that kill the sims (remedied with different hypre library)
+
+|| Nodes || Frames || Time to make 1 frame || Notes ||
+|| 32 || 32-39 || 3 hours || wall-time ran out ||
+|| 256 || 39-48 || 1 hours || memory died 48.4 ||
+|| 512 || 48-49 || 1 hours || memory died 49.5 ||
+|| '''32''' || '''49-50''' || '''4 hours''' || '''walltime ran out''' ||
+
+[[Image(chart_1.png)]]
+
+As the number of nodes increases, more patches are made, leading to more ghost zones. Thus, the global info as reported in standard out (that includes physical and ghost zones) increases with nodes.
+
+[[Image(chart_2.png)]]
+
+Peak goes down, as the amount of info is distributed over more and more cores.
+
+[[Image(chart_4.png)]]
+
+Percent efficiency as given in the standard out.
+
+
+[[Image(chart_3.png)]]
+
+The time to write to file increases with nodes. This can affect scaling computation (see http://astrobear.pas.rochester.edu/trac/astrobear/wiki/u/erica/ScalingBluestreak for details).
+
+The memory error is given in 2 places: 1) end of astrobear.log, and 2) a 'core' file that is written to the run directory. I am attaching as an example, the memory error reports for Shear15, nodes 256.