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


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

Legend:

Unmodified
Added
Removed
Modified
  • u/erica/ScalingBluestreak

    v1 v2  
    88|| 256 || 3:14 || 3:29, 3:42, 3:55, 4:09 || 13.3 min/ .1 frame || 6.8 min || .83 ||
    99|| 512 || 5:17 || 5:34, 5:47, 6:00, 6.13 || 13 min/ .1 frame || 9.4 min || 1.3 ||
     10
     11In the table, I do not include the first frame when averaging the run time as it seems unusually slow given the additional time to reload the frames upon restart.
     12
     13'''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.
     14
     15'''Frame / hour calculation:'''
     16
     17The 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.''
     18
     19'''32 Nodes Example'''
     20
     21[[latex($ R = [(33 - 1.9)*10 + 1.9 ]min\times \frac{1 ~hr}{60 ~min} = 5.2 ~\frac{hr}{frame} $)]]
     22
     23[[latex($ R^{-1} = 0.19 ~\frac{frames}{hour}$)]]
     24
     25'''Choosing the best set of runs:'''