Changes between Version 3 and Version 4 of 2020WP/ENHANCE-10_acc_fix_traqsr


Ignore:
Timestamp:
2020-05-13T22:55:02+02:00 (7 months ago)
Author:
acc
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • 2020WP/ENHANCE-10_acc_fix_traqsr

    v3 v4  
    220220 
    221221=== Performance and evaluation 
    222 Both these options produce identical results to the original code (based on an ORCA2_ICE_PISCES test using SETTE (which includes variable surface chlorophyll inputs. ln_timing was activated and the  
     222Both these options produce identical results to the original code (based on an ORCA2_ICE_PISCES test using SETTE (which includes variable surface chlorophyll inputs). ln_timing was activated and the CPU time (averaged across all processors) spent in tra_qsr used as a simple measure of performance. Unfortunately, variations in runtime between successive tests (even with the same code) on the NOC cluster were almost as great as any difference arising from algorithmic differences. Each test was repeated 6 times with the following results: 
     223 
     224|| code option    ||  
     225|| original code  ||  0.34      ||  0.34        ||  0.35        ||  0.35        ||  0.34        ||  0.34  ||     
     226||  minimum memory option ||  0.36      ||  0.36        ||  0.37        ||  0.36        ||  0.36        ||  0.37  ||  
     227|| low memory option ||  0.35   ||  0.35        ||  0.35        ||  0.36        ||  0.36        ||  0.35  || 
     228 
     229from which the tentative conclusion is that the minimum memory option does perform consistently worst but the low memory option appears to be a suitable replacement to the original code. More stringent tests are require to confirm this. 
     230 
    223231''...'' 
    224232