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. | 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 | + | 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. |
== Future SCEC data needs == | == Future SCEC data needs == | ||
| Line 11: | Line 11: | ||
Spring 2014: 45 TB (0.5 Hz, 286 sites, 1 combination, UCERF 3) | Spring 2014: 45 TB (0.5 Hz, 286 sites, 1 combination, UCERF 3) | ||
| − | == | + | == UCERF 2 == |
| − | + | For UCERF 2 we have about 15,000 ruptures statewide, or 7000 ruptures / 415000 rupture variations per site. | |
| − | === | + | === 0.5 Hz (per site), 2 component === |
| − | + | SGT data size: 40 GB | |
| − | + | SGT SUs (CPU): 8k | |
| − | + | PP number of tasks: 415k | |
| − | + | PP SUs: 1k | |
| − | + | Seismogram data size: 11 GB | |
| − | + | Total SUs: 9k | |
| − | + | Total data: 51 GB | |
| + | === 1 Hz (per site), 3 component === | ||
| − | + | SGT data size: 1.9 TB (large increase due to resampling fault surfaces at 250 m) | |
| − | + | SGT SUs (CPU): 192k | |
| − | + | SGT SUs (GPU): 27k | |
| − | + | PP number of tasks: 415k | |
| − | + | PP SUs: 48k | |
| − | + | Seismogram data size: 33 GB | |
| − | + | Total SUs: 240k CPU / 75k GPU | |
| − | + | Total data: 1.9 TB | |
| − | + | === 1.5 Hz (per site), 3 component === | |
| − | + | SGT data size: 2.8 TB | |
| − | + | SGT SUs (CPU): 648k | |
| − | + | SGT SUs (GPU): 93k | |
| − | |||
| − | + | PP number of tasks: 415k | |
| − | + | PP SUs: 72k | |
| − | + | Seismogram data size: 50 GB | |
| − | + | Total SUs: 720k CPU / 165k GPU | |
| − | + | Total data: 2.8 TB | |
| − | + | == UCERF 3 == | |
| − | + | For UCERF 3 we are expecting about 350000 ruptures statewide, or 163000 ruptures / 9.7 million rupture variations | |
| − | === | + | === 0.5 Hz (per site), 2 component === |
| − | + | SGT data size: 930 GB | |
| − | + | SGT SUs (CPU): 8k | |
| − | + | PP number of tasks: 9.7M | |
| − | + | PP SUs: 23k | |
| − | + | Seismogram data size: 256 GB | |
| − | + | Total SUs: 31k | |
| − | + | Total data: 1.1 TB | |
| − | == | + | === 1 Hz (per site), 3 component === |
| − | + | SGT data size: 44.5 TB | |
| − | |||
| − | + | SGT SUs (CPU): 192k | |
| − | + | SGT SUs (GPU): 27k | |
| − | + | PP number of tasks: 9.7M | |
| − | + | PP SUs: 1.1M | |
| − | + | Seismogram data size: 768 GB | |
| − | + | Total SUs: 240k CPU / 75k GPU | |
| − | + | Total data: 45.2 TB | |
| − | === 1 Hz, | + | === 1.5 Hz (per site), 3 component === |
| − | + | SGT data size: 65.4 TB | |
| − | + | SGT SUs (CPU): 648k | |
| − | SUs: | + | SGT SUs (GPU): 93k |
| − | + | PP number of tasks: 9.7M | |
| − | + | PP SUs: 1.7M | |
| − | + | Seismogram data size: 1.1 TB | |
| − | SUs: | + | Total SUs: 720k CPU / 165k GPU |
| + | |||
| + | Total data: 66.5 TB | ||
Revision as of 14:47, 28 June 2013
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.
Contents
Future SCEC data needs
These are estimates of CyberShake storage required on SCEC computers for upcoming runs.
July-August 2013: 6.1 TB to archive (0.5 Hz, CVM-SI, 2 SGT versions, 286 sites, UCERF 2) Fall 2013: 12 TB (1 Hz, 286 sites, 2 combinations, UCERF 2) Spring 2014: 45 TB (0.5 Hz, 286 sites, 1 combination, UCERF 3)
UCERF 2
For UCERF 2 we have about 15,000 ruptures statewide, or 7000 ruptures / 415000 rupture variations per site.
0.5 Hz (per site), 2 component
SGT data size: 40 GB
SGT SUs (CPU): 8k
PP number of tasks: 415k
PP SUs: 1k
Seismogram data size: 11 GB
Total SUs: 9k
Total data: 51 GB
1 Hz (per site), 3 component
SGT data size: 1.9 TB (large increase due to resampling fault surfaces at 250 m)
SGT SUs (CPU): 192k
SGT SUs (GPU): 27k
PP number of tasks: 415k
PP SUs: 48k
Seismogram data size: 33 GB
Total SUs: 240k CPU / 75k GPU
Total data: 1.9 TB
1.5 Hz (per site), 3 component
SGT data size: 2.8 TB
SGT SUs (CPU): 648k
SGT SUs (GPU): 93k
PP number of tasks: 415k
PP SUs: 72k
Seismogram data size: 50 GB
Total SUs: 720k CPU / 165k GPU
Total data: 2.8 TB
UCERF 3
For UCERF 3 we are expecting about 350000 ruptures statewide, or 163000 ruptures / 9.7 million rupture variations
0.5 Hz (per site), 2 component
SGT data size: 930 GB
SGT SUs (CPU): 8k
PP number of tasks: 9.7M
PP SUs: 23k
Seismogram data size: 256 GB
Total SUs: 31k
Total data: 1.1 TB
1 Hz (per site), 3 component
SGT data size: 44.5 TB
SGT SUs (CPU): 192k
SGT SUs (GPU): 27k
PP number of tasks: 9.7M
PP SUs: 1.1M
Seismogram data size: 768 GB
Total SUs: 240k CPU / 75k GPU
Total data: 45.2 TB
1.5 Hz (per site), 3 component
SGT data size: 65.4 TB
SGT SUs (CPU): 648k
SGT SUs (GPU): 93k
PP number of tasks: 9.7M
PP SUs: 1.7M
Seismogram data size: 1.1 TB
Total SUs: 720k CPU / 165k GPU
Total data: 66.5 TB
