GEOS-5 Run-Time Characteristics for Heracles 5.2

AGCM Performance at various resolutions

Results for a 10-day AMIP-style simulations at 72 levels using MERRA2 GOCART aerosols, MERRA-2 ocean, and running on Haswell CPUs. In this table, all were run with the same HISTORY collections, though at varying output resolutions.

Resolution CPUs (typical) Timestep (sec) Wall Clock (Hours) Throughput (Days per day) CPU Hours Typical Data Volume (GB) Notes
C12 (8°) 24 900 0.16 1380 5 4 Reynolds Ocean
C24 (~4°) 96 900 0.20 1340 23 6 Reynolds Ocean
C48 (~2°) 96 900 0.30 745 38 13
C90 (~1°) 96 900 0.65 383 73 38
C180 (~½°) 216 450 1.67 150 360 140
C360 (~¼°) 864 450 2.25 107 1980 530
C720 (14-km) 1536 225 8.15 26 12600 2090

AGCM Scaling for Cubed-Sphere Version at C180 (~½°, 2 day run)

Layout NX Layout NY Total PEs Total Time (sec) Dynamics Time (sec) Physics Time (sec) Dynamics Percent Physics Percent
6 36 216 1170 407 667 34.8% 57.0%
8 36 288 945 326 536 34.5% 56.7%
8 48 384 780 269 426 34.5% 54.6%
12 72 864 534 166 275 31.1% 51.5%

AOGCM Performance

Here we present two runs of Heracles 5.2 to compare coupled AOGCM to an AGCM run of the same atmospheric resolution but without coupled to MOM. The first line is the coupled AOGCM and the second is the pure AGCM. Results for a 10-day AMIP-style simulations at 72 atmospheric levels and 40 ocean levels using MERRA2 GOCART aerosols running on Haswell CPUs.

The large discrepancy in data volume is due to different HISTORY files being run, i.e., the coupled run output some ocean-specific collections the pure AGCM run did not. As always, data volume depends on the output requested by the user.

Atmos Res Ocean Res CPUs Timestep (sec) Wall Clock (Hours) Throughput (Days per day) CPU Hours Typical Data Volume (GB) Notes
C90 (1°) 720x410(½°) 180 900 0.92 261 205 85 Data size depends on HISTORY used
C90 (1°) dataocean 180 900 0.67 374 130 38 Data size depends on HISTORY used

Previous Models