Difference between revisions of "CyberShake Computational Estimates"
| (One intermediate revision by the same user not shown) | |||
| Line 4: | Line 4: | ||
The 0.5 Hz numbers are taken from Study 14.2. | The 0.5 Hz numbers are taken from Study 14.2. | ||
| + | |||
| + | The node-hours are estimates based on the XE6 and XK7 nodes on Blue Waters. | ||
== 1.0 Hz, 3 component == | == 1.0 Hz, 3 component == | ||
| Line 10: | Line 12: | ||
(38 GPU node-hrs per component) x (3 components) x (8 times the gridpoints) x (2 times the timesteps) x (20% more efficient due to more work per GPU) = 1460 node-hrs per site. | (38 GPU node-hrs per component) x (3 components) x (8 times the gridpoints) x (2 times the timesteps) x (20% more efficient due to more work per GPU) = 1460 node-hrs per site. | ||
| − | 23% of node hours to SGTs. | + | 23% of node hours to calculate SGTs. |
PP: At 0.5 Hz, it requires 41 CPU node-hrs per component. | PP: At 0.5 Hz, it requires 41 CPU node-hrs per component. | ||
(41 CPU node-hrs per components) x (3 components) x (25 times the rupture points) x (2 times the timesteps) x (20% more efficient due to rupture generator improvements) = 4920 node-hrs per site. | (41 CPU node-hrs per components) x (3 components) x (25 times the rupture points) x (2 times the timesteps) x (20% more efficient due to rupture generator improvements) = 4920 node-hrs per site. | ||
| − | 77% of node hours to PP. | + | 77% of node hours to calculate PP. |
| + | |||
| + | Each site requires about 550,000 rupture variations (410,000 x 4/3 for rupture variations v3.3) | ||
'''6380''' node-hours per 3-component site (181k core-hours) | '''6380''' node-hours per 3-component site (181k core-hours) | ||
Latest revision as of 15:52, 20 June 2014
We will describe or current best estimates for the CyberShake computational and data requirements as we progress in our simulation planning and testing. These estimates will help us identify which aspects of the CyberShake computational system needs to be optimized to work within our time and resource constraints.
The UCERF 3 estimates assume that the number of ruptures increases from 15,000 to 350,000, but the number of rupture variations per rupture on average remains the same.
The 0.5 Hz numbers are taken from Study 14.2.
The node-hours are estimates based on the XE6 and XK7 nodes on Blue Waters.
1.0 Hz, 3 component
SGTs: At 0.5 Hz, it requires 38 GPU node-hrs per component.
(38 GPU node-hrs per component) x (3 components) x (8 times the gridpoints) x (2 times the timesteps) x (20% more efficient due to more work per GPU) = 1460 node-hrs per site.
23% of node hours to calculate SGTs.
PP: At 0.5 Hz, it requires 41 CPU node-hrs per component.
(41 CPU node-hrs per components) x (3 components) x (25 times the rupture points) x (2 times the timesteps) x (20% more efficient due to rupture generator improvements) = 4920 node-hrs per site.
77% of node hours to calculate PP.
Each site requires about 550,000 rupture variations (410,000 x 4/3 for rupture variations v3.3)
6380 node-hours per 3-component site (181k core-hours)
1.82M node-hours for standard 3-component So Cal 286-site map (51.7M core-hours)
5.73M node-hours for increased density 3-component So Cal 898-site map (162M core-hours)
8.93M node-hours for statewide adaptive 3-component California 1400-site map (253M core-hours)
2.0 Hz
SGTs: At 1.0 Hz, it requires 485 GPU node-hrs per component.
(485 GPU node-hrs per component) x (3 components) x (8 times the gridpoints) x (2 times the timesteps) = 23.3k node-hrs per site.
PP: At 1.0 Hz, it requires 1640 CPU node-hrs per component.
(1640 CPU node-hrs per components) x (3 components) x (2 times the timesteps) = 9.8k node-hrs per site.
33.1k node-hours per 3-component site (686k core-hours)
9.47M node-hours for standard 3-component So Cal 286-site map (196M core-hours)
117M node-hours for increased density 3-component So Cal 3545-site map (2.4B core-hours)
46.3M node-hours for statewide adaptive 3-component California 1400-site map (960M core-hours)
