Changes between Version 2 and Version 3 of u/erica/ScalingBluestreak


Ignore:
Timestamp:
02/23/14 10:27:46 (11 years ago)
Author:
Erica Kaminski
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • u/erica/ScalingBluestreak

    v2 v3  
    1 '''Intro:''' All tests done with Shear15, ~1/4 way through simulation. I am assuming that the other runs will scale similarly. Astrobear was built with hypre library 2.9.0 without global partition.
    21
    3 '''Method:''' In global.data, changed number of frames and restart frame by factor of 10. So final frame went from 200 to 2000, and restart frame was changed from chombo00050.hdf to chombo00500.hdf. Running this simulation then produces frames with dt = 1/10th of original frame, which I then multiply run time by 10 to get an estimate of the run time per frame (see below).
     2== '''Intro:''' ==
     3All tests done with Shear15, ~1/4 way through simulation. I am assuming that the other runs will scale similarly. Astrobear was built with hypre library 2.9.0 without global partition.
     4
     5
     6== '''Method:''' ==
     7In global.data, changed number of frames and restart frame by factor of 10. So final frame went from 200 to 2000, and restart frame was changed from chombo00050.hdf to chombo00500.hdf. Running this simulation then produces frames with dt = 1/10th of original frame, which I then multiply run time by 10 to get an estimate of the run time per frame (see below).
    48
    59|| Nodes || Start time || Frame times || Average run time (not including first frame) || Avg. time to write to file || Frames/hr ||
    … …  
    1317'''Note that as I increase the number of nodes, the time to write to file increases as well.''' So to get an estimate of the time to write one frame, we need to be careful to remove the write time before multiplying by 10, and only after add it on.
    1418
    15 '''Frame / hour calculation:'''
     19
     20== '''Frame / hour calculation:''' ==
    1621
    1722The frame rate R in hour/frame is calculated as follows for the 32 node case. To get frames/hour, take the inverse R^-1^. ''This assumes the write time will be the same at the end of the normal dt frame rate.''
    … …  
    2328[[latex($ R^{-1} = 0.19 ~\frac{frames}{hour}$)]]
    2429
    25 '''Choosing the best set of runs:'''
     30
     31== '''Choosing the best set of runs:''' ==
     32