CyberShake Study 14.2 - Revision history

Scottcal: /* Application-level Metrics */

2022-02-02T18:56:16Z

Application-level Metrics

Scottcal at 16:43, 6 February 2018

2018-02-06T16:43:46Z

Scottcal at 20:36, 2 March 2016

2016-03-02T20:36:24Z

Maechlin: /* Presentations and Papers */

2014-10-15T23:40:54Z

Presentations and Papers

Maechlin: /* Technical Goals */

2014-10-15T23:40:23Z

Technical Goals

Scottcal: /* Performance Metrics */

2014-05-27T00:18:10Z

Performance Metrics

Scottcal: /* Performance Metrics */

2014-05-27T00:14:51Z

Performance Metrics

Scottcal: /* Performance Metrics */

2014-05-26T20:00:12Z

Performance Metrics

Scottcal: /* Performance Metrics */

2014-05-10T00:21:47Z

Performance Metrics

Maechlin at 19:25, 1 April 2014

2014-04-01T19:25:53Z

@@ Line 284: / Line 284: @@
 *286 sites
 *1144 pairs of SGTs
 *31463 jobs submitted to the Blue Waters queue
 *On average, 26 jobs were running, with a max of 60

@@ Line 9: / Line 9: @@
 Data products are available [[Study 14.2 Data Products | here]].
-The following parameters can be used to query the CyberShake database on focal.usc.edu for data products from this run:
+The SQLite database for this study is available at /home/scec-04/tera3d/CyberShake/sqlite_studies/study_14_2/study_14_2.sqlite .  It can be accessed using a SQLite client.
   Hazard_Dataset_IDs: 34 (CVM-H, no GTL, AWP-ODC CPU), 35 (CVM-S4.26, AWP-ODC GPU), 37 (CVM-S4.26, AWP-ODC CPU), 38 (BBP 1D model, AWP-ODC CPU)

@@ Line 1: / Line 1: @@
-CyberShake Study 14.2 is a computational study to calculate physics-based probabilistic seismic hazard curves under 4 different conditions: CVM-S4.26 with CPU, CVM-S4.26 with GPU, a 1D model with CPU, and CVM-H without a GTL with GPU.  It uses the Graves and Pitarka (2010) rupture variations and the UCERF2 ERF.  Both the SGT calculations and the post-processing will be done on Blue Waters.  The goal is to calculate the standard Southern California site list (286 sites) used in previous CyberShake studies so we can produce comparison curves and maps, and understand the impact of the SGT codes and velocity models on the CyberShake seismic hazard.
+CyberShake Study 14.2 is a computational study to calculate physics-based probabilistic seismic hazard curves under 4 different conditions: CVM-S4.26 with CPU, CVM-S4.26 with GPU, a 1D model with GPU, and CVM-H without a GTL with CPU.  It uses the Graves and Pitarka (2010) rupture variations and the UCERF2 ERF.  Both the SGT calculations and the post-processing will be done on Blue Waters.  The goal is to calculate the standard Southern California site list (286 sites) used in previous CyberShake studies so we can produce comparison curves and maps, and understand the impact of the SGT codes and velocity models on the CyberShake seismic hazard.
-The system is a heterogenous Cray XE6/XK7 consisting of more than 22,000 XE6 compute nodes (eachcontaining two AMD Interlagos processors) augmented by more than 4000 XK7 compute nodes (each containing one AMDInterlagos processor and one NVIDIA GK110 "Kepler" accelerator) in a single high speed Gemini interconnection fabric.
+The system is a heterogenous Cray XE6/XK7 consisting of more than 22,000 XE6 compute nodes (each containing two AMD Interlagos processors) augmented by more than 4000 XK7 compute nodes (each containing one AMDInterlagos processor and one NVIDIA GK110 "Kepler" accelerator) in a single high speed Gemini interconnection fabric.
 == Computational Status ==
@@ Line 10: / Line 10: @@
 The following parameters can be used to query the CyberShake database on focal.usc.edu for data products from this run:
   CVM-S4.26:  Velocity Model ID 5

@@ Line 436: / Line 436: @@
 [http://hypocenter.usc.edu/research/cybershake/Study_14_2_Technical_Readiness_Review.pptx Technical Readiness Review]
-[http://hypocenter.usc.edu/research/BlueWaters/TTS_v11.pdf Time To Solution Summary (pdf)]
+[http://hypocenter.usc.edu/research/BlueWaters/TTS_v12.pdf Time To Solution Summary (pdf)]
-[http://hypocenter.usc.edu/research/BlueWaters/TTS_v11.docx Time To Solution Summary (docx)]
+[http://hypocenter.usc.edu/research/BlueWaters/TTS_v12.docx Time To Solution Summary (docx)]
 [http://hypocenter.usc.edu/research/BlueWaters/TTS_v11.xlsx Time To Solution Speadsheet (xlsx)[]

@@ Line 33: / Line 33: @@
 #Show that Blue Waters can be used to perform both the SGT and post-processing phases
-#Recalculate Performance Metrics for CyberShake Calculation - [http://hypocenter.usc.edu/research/BlueWaters/TTS_v10.pdf CyberShake Time to Solution Description]
+#Recalculate Performance Metrics for CyberShake Calculation - [http://hypocenter.usc.edu/research/BlueWaters/TTS_v12.pdf CyberShake Time to Solution Description]
 #Compare the performance and queue times when using AWP-ODC-SGT CPU vs AWP-ODC-SGT GPU codes.

@@ Line 290: / Line 290: @@
 *On average, 1620 nodes were used (49,280 cores)
 **On average, 1460 XE nodes were used, with a max of 9220
-**On average, 160 XK nodes were used (51,325/, with a max of 1100
+**On average, 225 XK nodes were used (51,325/228), with a max of 1100
 *Delay per job (using a 1-day, no restarts cutoff: 804 workflows, 23658 jobs) was mean: 1052 sec, median: 191, min: 130, max: 59721, sd: 3081.
 {| border="1" align="center"

@@ Line 267: / Line 267: @@
 A reservation for 700 XE nodes and 200 XK nodes began at 7 am PST on 2/18/14.
-XK reservation was released at 21:18 CST on 2/24/14 (156 hrs)
+XK reservation was released at 21:18 CST on 2/24/14 (156 hrs).  Continued to run 72 hours (total of 228).
-XE reservation expired at 19:30 CST on 3/3/14 (322 hrs).
+XE reservation expired at 19:30 CST on 3/3/14 (322 hrs). Continued to run 20 hours.
 After the run completed, Blue Waters reports 34667 (System Status -> Usage) or 46687 (Your Blue Waters -> Jobs) jobs and 700,908.08 total node hours executed by scottcal.
@@ Line 290: / Line 290: @@
 *On average, 1620 nodes were used (49,280 cores)
 **On average, 1460 XE nodes were used, with a max of 9220
-**On average, 160 XK nodes were used, with a max of 1100
+**On average, 160 XK nodes were used (51,325/, with a max of 1100
 *Delay per job (using a 1-day, no restarts cutoff: 804 workflows, 23658 jobs) was mean: 1052 sec, median: 191, min: 130, max: 59721, sd: 3081.
 {| border="1" align="center"

@@ Line 390: / Line 390: @@
                  Runtime: mean 1393.000000, median: 1309.000000, min: 6.000000, max: 3293.000000, sd: 299.041418
                  Attempts: mean 1.026770, median: 1.000000, min: 1.000000, max: 11.000000, sd: 0.257591
+                Tasks submitted (6948 jobs): mean 14364.293034, median 14419.000000, min 0.000000, max 15405.000000, sd 1322.353212
 *Load_Amps (1153 jobs):
                  Runtime: mean 416.934952, median: 404.000000, min: 236.000000, max: 711.000000, sd: 59.657596