Difference between revisions of "CyberShake Computational Estimates"
| Line 1: | Line 1: | ||
| − | + | 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. | |
| − | |||
| − | |||
== SGT Simulation Parameters == | == SGT Simulation Parameters == | ||
| Line 9: | Line 7: | ||
Mesh Size Mesh Pts 12,000,000,000 320 | Mesh Size Mesh Pts 12,000,000,000 320 | ||
Time Steps 40,000 | Time Steps 40,000 | ||
| − | |||
Total Sites 4240 | Total Sites 4240 | ||
| Line 20: | Line 17: | ||
Estimated Effeciency Jagaur 8-10% | Estimated Effeciency Jagaur 8-10% | ||
| − | + | Jaguar 2.6GHz x 4FPU 10.4Gflop/s per core | |
Blue Waters 4GHz x 8 FPUs 32Gflop/s per core | Blue Waters 4GHz x 8 FPUs 32Gflop/s per core | ||
| + | |||
</pre> | </pre> | ||
Revision as of 05:23, 20 February 2011
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.
Contents
SGT Simulation Parameters
1Hz CyberShake Estimates 2010.11.1 Max Freq 1Hz Mesh Size Mesh Pts 12,000,000,000 320 Time Steps 40,000 Total Sites 4240 Total CPU Hours 320M Estimated BW 10+Pflop/s Estimated 1Hz Jaguar (half machine) 120 Days Esimated 1Hz BW 40 Days Estimated Effeciency Jagaur 8-10% Jaguar 2.6GHz x 4FPU 10.4Gflop/s per core Blue Waters 4GHz x 8 FPUs 32Gflop/s per core
Southern California, 0.5 Hz (current functionality)
Sites: 223 sites (802 on 5 km grid)
Jobs: 190 million
CPU-hours: 5.5 million (Ranger)
Data products (seismograms, spectral acceleration): 2.1 TB
Runtime on half-Ranger: 174 hrs (7.3 days)
Runtime on half-Jaguar: 40 hrs (1.7 days)
Runtime on half-BW(=half-Mira): 10 hrs
Database entries: 366 million
Southern California, 1.0 Hz
AWP-ODC
Sites: 223 sites
Jobs: 190 million
CPU-hours: 19.3 million (Ranger)
Data products (seismograms, spectral acceleration): 4.0 TB
Runtime on half-Ranger: 613 hrs (25.5 days)
Runtime on half-Jaguar: 142 hrs (5.9 days)
Runtime on half-BW(=half-Mira): 35 hrs (1.5 days)
Database entries: 366 million
California, 0.5 Hz
Current software
Sites: 4240
Jobs: 3.6 billion
CPU-hours: 104.6 million (Ranger)
Data products (seismograms, spectral acceleration): 39.9 TB
Runtime on half-Ranger: 3322 hrs (138.4 days)
Runtime on half-Jaguar: 771 hrs (32.2 days)
Runtime on half-BW(=half-Mira): 192 hrs (8 days)
Database entries: 6.95 billion
With AWP-ODC
Sites: 4240
Jobs: 3.6 billion
CPU-hours: 83.5 million (Ranger)
Data products (seismograms, spectral acceleration): 39.9 TB
Runtime on half-Ranger: 2652 hrs (110.5 days)
Runtime on half-Jaguar: 616 hrs (25.7 days)
Runtime on half-BW(=half-Mira): 153 hrs (6.4 days)
Database entries: 6.95 billion
California, 1.0 Hz
AWP-ODC
Jobs: 3.6 billion
CPU-hours: 376.2 million (337.8 million - SGT generation only, 339.1 million - SGT workflow)
Data products (seismograms, spectral acceleration): 76.5 TB
Runtime on half-Ranger: 11947 hrs (497.8 days)
Runtime on half-Jaguar: 3096 hrs (129 days)
Runtime on half-BW(=half-Mira): 770 hrs (32.1 days) (4.3% of yearly CPU-hrs)
Database entries: 6.95 billion
