View source for Timing tests with GEOS-Chem 12.0.0

== Overview ==

The GEOS-Chem Support Team has created a timing test package that you can use to determine the performance of GEOS-Chem on your system.  The time test runs the [[GEOS-Chem 12#12.0.0|GEOS-Chem 12.0.0 release code]] (in GEOS-Chem "Classic" mode) for 7 model days with the "Standard" chemistry mechanism.  Our experience has shown that a 7-day simulation will give a more accurate timing result than a 1-day simulation.  This is because much of the file I/O (i.e. HEMCO reading annual or monthly-mean emissions fields) occurs on the first day of a run.

=== Installation ===

If you haven't already, download the [[GEOS-Chem 12#12.0.0|GEOS-Chem 12.0.0]] source code and unit tester using:

 # Get the GEOS-Chem 12.0.0 source code
 git clone https://github.com/geoschem/geos-chem Code.12.0.0
 cd Code.12.0.0
 git checkout -b 12.0.0
 cd ..
 
 # Get the GEOS-Chem 12.0.0 unit tester
 git clone https://github.com/geoschem/geos-chem-unittest UT
 cd UT
 git checkout -b 12.0.0+PrintTimeFix

NOTE: Checking out the tag '''12.0.0+PrintTimeFix''' will make sure that you have an updated version of the <tt>printTime</tt> script, which is used to print out the results from a time test simulation log file.

Create your run directory using the GEOS-Chem UnitTest by following [[Creating_GEOS-Chem_run_directories|these instructions]]. To copy the <tt>gc_timing</tt> run directory, make sure you have the following lines in your <tt>CopyRunDirs.input</tt> file:

 #--------|-----------|------|------------|------------|------------|---------|
 # MET    | GRID      | NEST | SIMULATION | START DATE | END DATE   | EXTRA?  |
 #--------|-----------|------|------------|------------|------------|---------|
  geosfp   4x5         -      gc_timing    2016070100   2016070800   -

Also make sure to

=== Compilation (versions 12.0.0 thru 12.5.0) ===

To build the code for the timing tests, you must first clean the source code and run directory of any files left over from a previous run:
 
  cd geosfp_4x5_gc_timing
  make superclean

If you wish to perform a timing test using the [[List of diagnostics archived to bpch format|binary punch (aka bpch) diagnostics]], use this command to build GEOS-Chem:

  make -j4 TIMERS=1 mpbuild 2>&1 log.build

Or if you wish to perform a timing test using the [[List of diagnostics archived to netCDF format|netCDF diagnostics]], use this command:

  make -j4 NC_DIAG=y TIMERS=1 mpbuild 2>&1 log.build

Information about the options used for the compilation (as well as the compiler version) will be printed to the file <tt>lastbuild.mp</tt>.

=== Compilation (versions 12.6.0 and later) ===

'''NOTE: In GEOS-Chem 12.6.0 the compiling commands were changed  The mpbuild target was replaced with build.'''

To build the code for the timing tests, you must first clean the source code and run directory of any files left over from a previous run:
 
  cd geosfp_4x5_gc_timing
  make superclean

If you wish to perform a timing test using the [[List of diagnostics archived to bpch format|binary punch (aka bpch) diagnostics]], use this command to build GEOS-Chem:

  make -j4 TIMERS=1 build

Information about the options used for the compilation (as well as the compiler version) will be printed to the GEOS-Chem_log_files#The_lastbuild_file<tt>|lastbuild</tt> log file]].  Also, the output of the compilation will be sent to [[GEOS-Chem_log_files#compile.log_file|<tt>compile.log</tt>]].

=== Performing the timing test ===

To run the code, follow the instructions in the 

  geosfp_4x5_gc_timing/README 

file.  We have provided sample run scripts that you can use to submit jobs:

  geosfp_4x5_gc_timing/doTimeTest          # Submit job directly
  geosfp_4x5_gc_timing/doTimeTest.slurm    # Submit job using the SLURM scheduler  
  geosfp_4x5_gc_timing/doTimeTest.pbs      # Submit job using the PBS scheduler (in GEOS-Chem 12.7.0 and later)

'''''Special instructions for using SLURM'''''

<blockquote>As described in the README file, if you are going to submit a time test via the SLURM scheduler, please take a moment to edit the <tt>#SBATCH</tt> tags at the top of the <tt>doTimeTest.slurm</tt> file:</blockquote>

         #SBATCH -c NUMBER_OF_CORES
         #SBATCH -N 1
         #SBATCH -t 06:00:00
         #SBATCH -p PARTITION NAME
         #SBATCH --mem=10000
         #SBATCH --exclusive
         #SBATCH --mail-type=ALL
         #SBATCH --mail-user=MY_EMAIL_ADDRESS
         #SBATCH -o ./doTimeTest.log.%j
         #SBATCH -e ./doTimeTest.log.%j

<blockquote>Replace
*<tt>NUMBER_OF_CORES</tt> with the number of cores that your time test will use,
*<tt>PARTITION_NAME</tt> with the name of the queue that your simulation will run in, and
*<tt>MY_EMAIL_ADDRESS</tt> with the email address where you will receive SLURM notifications.

Also note: We recommend to leave the <tt>#SBATCH --exclusive</tt> tag.  This will reserve a whole node for the run, even if you do not use all of the cores on the node.  This will yield in more accurate timing results, as it will prevent other jobs from "backfilling" onto the node.

To submit the job, type:</blockquote>

        sbatch doTimeTest.slurm

The regular GEOS-Chem output as well as timing information will be sent to a log file named:

  doTimeTest.log.ID

where ID is either the SLURM job ID # or the process ID.

=== Displaying the test results ===

You can print out the timing results with the <tt>printTime</tt> script:

  cd geosfp_4x5_gc_timing
  ./printTime doTimeTest.log.ID

which will display results similar to this:

 GEOS-Chem 7-Model-Day Time Test Results
 ===============================================================================
 
 Machine information
 -------------------------------------------------------------------------------
 Machine or node name: : holy7c19114.rc.fas.harvard.edu
 CPU vendor            : GenuineIntel
 CPU model name        : Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
 CPU speed [MHz]       : 2557.160
 
 GEOS-Chem information
 -------------------------------------------------------------------------------
 GEOS-Chem Version     : 12.0.0
 Last commit           : Remove obsolete, commented-out code from several modules 
 Commit date           : Thu Aug 9 16:59:22 2018 -0400 
 Compiler version      : gfortran 7.1.0
 Compilation options   : geosfp 4x5 standard traceback bpch_diag no_reduced timers
 
 Simulation information
 -------------------------------------------------------------------------------
 Simulation start date : 20160701 000000
 Simulation end date   : 20160708 000000
 Number of CPUs used   : 12
 Total CPU time  [s]   : 82657.95
 Wall clock time [s]   : 9090.28
 CPU / Wall ratio      : 9.093
 % of ideal performace : 75.78

You can then use these results to fill in [[#Table of 7-model-day run times|the table below]].

--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 20:18, 13 August 2018 (UTC)

== Table of 7-model-day run times ==

The following timing test results were done with the '''"out-of-the-box" [[GEOS-Chem 12#12.0.0|GEOS-Chem 12.0.0]] release''' code configuration.

*All jobs used [[GEOS-FP]] meteorology at 4&deg; x 5&deg; resolution.  
*Jobs started on model date <tt>2016/07/01 00:00 GMT</tt> and finished on <tt>2016/07/08 00:00 GMT</tt>.
*The code was compiled from the run directory (<tt>geosfp_4x5_gc_timing</tt>) with one of the standard options:
**<tt>make -j4 TIMERS=1 mpbuild</tt>
***This sets: <tt>MET=geosfp GRID=4x5 CHEM=Standard UCX=y NO_REDUCED=n TRACEBACK=n BOUNDS=n FPE=n DEBUG=n NO_ISO=n NEST=n BPCH_DIAG=y</tt>
**<tt>make -j4 NC_DIAG=y TIMERS=1 mpbuild</tt>
***This sets: <tt>MET=geosfp GRID=4x5 CHEM=Standard UCX=y NO_REDUCED=n TRACEBACK=n BOUNDS=n FPE=n DEBUG=n NO_ISO=n NEST=n NC_DIAG=y</tt>
**All timing test jobs are assumed to use binary punch diagnostics (<tt>BPCH_DIAG=y</tt>) by default except where otherwise noted.
*Wall clock times are listed from '''fastest to slowest''', for the same number of CPUs.
*It's OK to round CPU and wall clock times to the nearest second, for clarity.
*Feel free to add your own results below!

=== Timing tests using 32 cores ===

{| border=1 cellspacing=0 cellpadding=5 
|-valign="top" bgcolor="#CCCCCC"
!width="150px"|Submitter
!width="200px"|Machine or Node<br>and Compiler
!width="100px"|CPU vendor
!width="160px"|CPU model
!width="75px"|Speed [MHz]
!width="85px"|CPU time
!width="85px"|Wall time
!width="75px"|CPU / Wall<br>ratio
!width="60px"|% ideal
!width="200px"|Notes

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c09216.rc.fas.harvard.edu<br>ifort 17.0.4
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1672.289
|136933<br>'''38:02:13'''
|4654<br>'''01:17:35'''
|29.425
|91.95%
|BPCH_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c13205.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1227.925
|113147<br>'''31:25:48'''
|5338<br>'''01:28:59'''
|21.198
|66.24%
|BPCH_DIAG=y TIMERS=1<br>-ffast-math

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c13209.rc.fas.harvard.edu<br>ifort 17.0.4
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1252.453
|151201<br>'''42:00:00'''
|5539<br>'''01:32:20'''
|27.296
|85.30%
|NC_DIAG=1 TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c15105.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1235.964
|122252<br>'''33:57:32'''
|5721<br>'''01:35:20'''
|21.370
|66.78%
|BPCH_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c15106.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1262.871
|123799<br>'''34:23:20'''
|6207<br>'''01:43:26'''
|19.946
|62.33%
|NC_DIAG=y TIMERS=1


|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c07106.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1200.117
|122860<br>'''34:07:41 '''
|6307<br>'''01:45:07'''
|20.196
|63.11%
|NC_DIAG=y TIMERS=1<br>-ffast-math

|}

=== Timing tests using 24 cores ===

{| border=1 cellspacing=0 cellpadding=5 
|-valign="top" bgcolor="#CCCCCC"
!width="150px"|Submitter
!width="200px"|Machine or Node<br>and Compiler
!width="100px"|CPU vendor
!width="160px"|CPU model
!width="75px"|Speed [MHz]
!width="85px"|CPU time
!width="85px"|Wall time
!width="75px"|CPU / Wall<br>ratio
!width="60px"|% ideal
!width="200px"|Notes

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c19112.rc.fas.harvard.edu<br>ifort 17.0.4
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2679.878
|114550<br>'''31:49:09'''
|5181<br>'''01:26:20'''
|22.108
|92.12%
|BPCH_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c15104.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1298.472
|93157<br>'''25:52:37'''
|5697<br>'''01:34:55'''
|16.353
|68.14%
|BPCH_DIAG=y TIMERS=1<br>-ffast-math

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c19106.rc.fas.harvard.edu<br>ifort 17.0.4
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2704.898
|122925<br>'''34:08:46'''
|6004<br>'''01:40:05'''
|20.473
|85.31%
|NC_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c11214.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2781.843
|101403<br>'''28:10:01'''
|6139<br>'''01:42:18'''
|16.518
|68.82%
|BPCH_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c17304.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2999.964
|99394.14<br>'''27:36:32'''
|6353.72<br>'''01:45:54'''
|15.529
|64.70%
|NC_DIAG=y TIMERS=1<br>-ffast-math

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c11215.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2757.48
|103622<br>'''28:47:02'''
|6680<br>'''01:51:18'''
|15.513
|64.64%
|NC_DIAG=y TIMERS=1

|}

=== Timing tests using 16 cores ===

{| border=1 cellspacing=0 cellpadding=5 
|-valign="top" bgcolor="#CCCCCC"
!width="150px"|Submitter
!width="200px"|Machine or Node<br>and Compiler
!width="100px"|CPU vendor
!width="160px"|CPU model
!width="75px"|Speed [MHz]
!width="85px"|CPU time
!width="85px"|Wall time
!width="75px"|CPU / Wall<br>ratio
!width="60px"|% ideal
!width="200px"|Notes

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c05205.rc.fas.harvard.edu<br>ifort 17.0.4
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2729.835
|88891<br>'''24:41:31'''
|5887<br>'''01:38:06'''
|15.100
|94.38%
|NC_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c17316.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1490.015
|78153<br>'''21:42:32'''
|6726<br>'''01:52:05'''
|11.443
|71.52%
|BPCH_DIAG=y TIMERS=1<br>-ffast-math
*NOTE: Might have been affected by /n/regal disk issues

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c03315.rc.fas.harvard.edu<br>ifort 17.0.4
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2536.242
|102716<br>'''28:31:53'''
|6933<br>'''01:55:34'''
|14.815
|92.59%
|BPCH_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c09215.rc.fas.harvard.edu<br>ifort 17.0.4
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2499.984
|100401<br>'''27:53:20 '''
|7086<br>'''01:58:05 '''
|14.169
|88.56%
|NC_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c15302.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1295.929
|87989<br>'''24:26:28'''
|7455<br>'''02:04:16'''
|11.802
|73.76%
|BPCH_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c13209.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2600.554
|97272<br>'''27:01:12'''
|8871<br>'''02:27:50'''
|10.965
|68.53%
|NC_DIAG=y TIMERS=1<br>-ffast-math
*NOTE: Might have been affected by /n/regal disk issues

|}

=== Timing tests using 12 cores ===

{| border=1 cellspacing=0 cellpadding=5 
|-valign="top" bgcolor="#CCCCCC"
!width="150px"|Submitter
!width="200px"|Machine or Node<br>and Compiler
!width="100px"|CPU vendor
!width="160px"|CPU model
!width="75px"|Speed [MHz]
!width="85px"|CPU time
!width="85px"|Wall time
!width="75px"|CPU / Wall<br>ratio
!width="60px"|% ideal
!width="200px"|Notes

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c05210.rc.fas.harvard.edu<br>ifort 17.0.4
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2499.984
|76898<br>'''21:21:36'''
|6666<br>'''01:51:11'''
|11.536
|96.13%
|BPCH_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c13313.rc.fas.harvard.edu<br>gfortran 7.1
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1294.699
|63631<br>'''17:38:42'''
|6945<br>'''01:55:44'''
|9.163
|76.35%
|BPCH_DIAG=y TIMERS=1<br>-ffast-math

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c13310.rc.fas.harvard.edu<br>gfortran 7.1
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2599.98
|69639<br>'''19:20:39'''
|7899<br>'''02:11:39'''
|8.816
|73.47%
|NC_DIAG=y TIMERS=1<br>-ffast-math

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c03303.rc.fas.harvard.edu<br>ifort 17.0.4
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1994.097
|84611<br>'''23:30:10'''
|7943<br>'''02:12:21'''
|10.653
|88.77%
|NC_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c05310.rc.fas.harvard.edu<br>gfortran 7.1
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2599.980
|76182<br>'''21:09:43'''
|8577<br>'''02:25:55'''
|8.882
|70.93%
|NC_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c19114.rc.fas.harvard.edu<br>gfortran 7.1
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2557.16
|82658<br>'''22:57:40'''
|9090<br>'''02:31:30'''
|9.093
|75.78%
|BPCH_DIAG=y TIMERS=1
*NOTE: Might have been affected by issues on /n/regal disk

|}

=== Timing tests using 8 cores ===

{| border=1 cellspacing=0 cellpadding=5 
|-valign="top" bgcolor="#CCCCCC"
!width="150px"|Submitter
!width="200px"|Machine or Node<br>and Compiler
!width="100px"|CPU vendor
!width="160px"|CPU model
!width="75px"|Speed [MHz]
!width="85px"|CPU time
!width="85px"|Wall time
!width="75px"|CPU / Wall<br>ratio
!width="60px"|% ideal
!width="200px"|Notes

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c03103.rc.fas.harvard.edu<br>ifort 17.0.4
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2727.375
|67163<br>'''18:39:21'''
|8738<br>'''02:25:37'''
|7.687
|96.08%
|BPCH_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c01105.rc.fas.harvard.edu<br>ifort 17.0.4
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1900.253
|68464<br>'''19:01:05'''
|9266<br>'''02:34:26'''
|7.389
|92.36%
|NC_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c01114.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2944.265
|60457<br>'''16:47:44 '''
|9584<br>'''02:39:43 '''
|6.308
|78.85%
|BPCH_DIAG=y TIMERS=1<br>-ffast-math

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c07108.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1258.769
|60566<br>'''16:49:26 '''
|9734<br>'''02:42:14 '''
|6.222
|77.77%
|NC_DIAG=y TIMERS=1<br>-ffast-math

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c05310.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1293.222
|65767<br>'''18:16:27'''
|10084<br>'''02:48:04'''
|6.522
|81.53%
|BPCH_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c17102.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1500.433
|66796<br>'''18:33:16'''
|10642<br>'''02:57:22'''
|6.277
|78.46%
|NC_DIAG=y TIMERS=1

|}

=== Timing tests using 4 cores ===

{| border=1 cellspacing=0 cellpadding=5 
|-valign="top" bgcolor="#CCCCCC"
!width="150px"|Submitter
!width="200px"|Machine or Node<br>and Compiler
!width="100px"|CPU vendor
!width="160px"|CPU model
!width="75px"|Speed [MHz]
!width="85px"|CPU time
!width="85px"|Wall time
!width="75px"|CPU / Wall<br>ratio
!width="60px"|% ideal
!width="200px"|Notes

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c01106.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1200.117
|48795<br>'''13:33:14'''
|14155<br>'''03:55:55'''
|3.447
|86.18%
|BPCH_DIAG=y TIMERS=1<br>-ffast-math

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c11216.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2499.984
|49472<br>'''13:44:31'''
|14155<br>'''03:58:55'''
|3.451
|86.28%
|NC_DIAG=y TIMERS=1<br>-ffast-math

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c01113.rc.fas.harvard.edu<br>ifort 17.0.4
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|2915.554
|56866<br>'''15:47:46'''
|14810<br>'''04:06:50'''
|3.840
|95.99%
|NC_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c17111.rc.fas.harvard.edu<br>ifort 17.0.4
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1631.191
|55835<br>'''15:30:35'''
|15553<br>'''04:19:13'''
|3.590
|89.75%
|BPCH_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c05310.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1293.222
|56953<br>'''15:49:13'''
|16097<br>'''04:28:17'''
|3.54
|88.45%
|BPCH_DIAG=y TIMERS=1

|-valign="top" 
|Bob Yantosca (Harvard)
|holy7c17102.rc.fas.harvard.edu<br>gfortran 7.1.0
|GenuineIntel
|Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
|1500.433
|59050<br>'''16:24:10'''
|17037<br>'''04:43:57'''
|3.466
|86.65%
|NC_DIAG=y TIMERS=1

|}

== Graphs of 7-model-day run times ==

=== Scalability across cores ===

[[File:Scalability 7day 12.0.0.png]]

The above plot shows the run times for various [[GEOS-Chem 12#12.0.0|GEOS-Chem "Classic" 12.0.0]] configurations.  Bob Yantosca generated the above plot using the timing results listed in the table above.  For a more in-depth analysis of these timing results, [[Media:GEOS-Chem_12.0.0_timing_results.pdf|please see this presentation]].

--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 20:32, 16 August 2018 (UTC)

=== Time spent in each GEOS-Chem operation ===

[[File:Ops_gf_bpch_12.0.0.png]]

[[File:Ops_gf_nc_12.0.0.png]]

The above plots show how much time is spent in each GEOS-Chem operation for several different [[GEOS-Chem 12#12.0.0|GEOS-Chem "Classic" 12.0.0]] configurations.  Bob Yantosca generated the above plots using the timing results listed in the table above.  For a more in-depth analysis of these timing results, [[Media:GEOS-Chem_12.0.0_timing_results.pdf|please see this presentation]].

--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 20:43, 16 August 2018 (UTC)

== GCHP timing tests ==

Help us pool performance information across systems by contributing your GCHP run information on [[GCHP Timing Tests|our ''GCHP Timing Tests'' page]].

--[[User:Bmy|Bob Yantosca]] ([[User talk:Bmy|talk]]) 17:58, 17 August 2018 (UTC)