Difference between revisions of "GEOS-Chem 1-month benchmark timing results"
From Geos-chem
| Line 1: | Line 1: | ||
| − | + | == Overview == | |
| − | + | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
On this page, we provide timing results obtained from 1-month benchmark GEOS-Chem simualtions. | On this page, we provide timing results obtained from 1-month benchmark GEOS-Chem simualtions. | ||
| Line 22: | Line 14: | ||
Timing information is obtained from the GEOS-Chem "Timers" output, which is printed to the log file. Timers output is activated by setting <tt>use_gcclassic_timers: true</tt> in geoschem_config.yml. | Timing information is obtained from the GEOS-Chem "Timers" output, which is printed to the log file. Timers output is activated by setting <tt>use_gcclassic_timers: true</tt> in geoschem_config.yml. | ||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 18:12, 24 October 2023
Overview
On this page, we provide timing results obtained from 1-month benchmark GEOS-Chem simualtions.
Timing results from 1-month benchmarks
To access the entire history of GEOS-Chem benchmarks, please see our GEOS-Chem versions page.
Wall time spent in model components
The above plot displays the "wall clock" time spent in each model component as observed in the GEOS-Chem timers output from recent public and internal 1-month benchmark simulations (Credit: Melissa Sulprizio). This type of plot can be very helpful in determining if updates made to GEOS-Chem cause significant computational bottlenecks.
Timing information is obtained from the GEOS-Chem "Timers" output, which is printed to the log file. Timers output is activated by setting use_gcclassic_timers: true in geoschem_config.yml.
