Changes between Version 18 and Version 19 of ticket/1611_is_oce_cpl


Ignore:
Timestamp:
2015-10-06T17:26:48+02:00 (5 years ago)
Author:
mathiot
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • ticket/1611_is_oce_cpl

    v18 v19  
    88'''ticket''' : XXXX 
    99 
    10 '''Branch''' : [https://forge.ipsl.jussieu.fr/nemo/browser/branches/NERC/dev_r5589_is_oce_cpl   dev_r5589_is_oce_cpl ] (copy of trunk at r5589. 
     10'''Branch''' : [https://forge.ipsl.jussieu.fr/nemo/browser/branches/NERC/dev_r5589_is_oce_cpl   dev_r5589_is_oce_cpl ] (copy of trunk at r5589). 
    1111---- 
    1212 
     
    115115The call of these routines is done only during the restart step. I described below the change of the istate routines timing as well as the memory: 
    116116 * With coupling after modification: istate = XXXX 
    117  * Without coupling after  modification: istate = 0.01 s 
    118  * Without coupling before modification: istate = 0.01 s 
     117 * Without coupling after  modification: istate = XXX s 
     118 * Without coupling before modification: istate = XXX s 
    119119 
    120  * Overall timing/memory before modification (ORCA2-LIM3 SETTE config): CPU time: 643 s/ Max resident set size: 480 592 kb 
    121  * Overall timing/memory after  modification (ORCA2-LIM3 SETTE config): CPU time: 680 s/ Max resident set size: 482 432 kb 
     120 * Overall timing (nn_timing == 1)/memory (time -v) before modification (ORCA2-LIM3 SETTE config): CPU time: XXXX s / Max resident set size: 480 592 kb 
     121 * Overall timing (nn_timing == 1)/memory (time -v) after  modification (ORCA2-LIM3 SETTE config): CPU time: XXXX s / Max resident set size: 480 365 kb 
     122 
     123Some issue related to timing.output: some crap number (negative number) + lot a variability between 2 similar jobs 
    122124 
    123125----