Changes between Version 8 and Version 9 of OfflineAddingMemoryandTimingInformation
- Timestamp:
- May 18, 2025, 7:55:45 PM (7 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OfflineAddingMemoryandTimingInformation
v8 v9 35 35 The output will look like this: 36 36 {{{ 37 PDAF Memory overview 38 --------------------------------------------- 39 Allocated memory (MB) 40 state and U: 0.59617 MB (persistent) 41 ensemble array: 0.64087 MB (persistent) 42 analysis step: 6.05578 MB (temporary) 43 resampling: 2.81129 MB (temporary) 37 PDAF PDAF Memory overview 38 PDAF --------------------------------------------- 39 PDAF Allocated memory (MiB) 40 PDAF state and A: 2.000 MiB (persistent) 41 PDAF ensemble array: 16.000 MiB (persistent) 42 PDAF analysis step: 0.757 MiB (temporary) 43 PDAF PDAF-OMI: 0.521 MiB (temporary) 44 44 45 }}} 45 46 46 47 This memory information shows only the memory required by a single filter processes. In the example codes, this is the process with `mype_world=0`. One can also display the overall allocated memory by adding 47 48 {{{ 48 IF (mype_world==0)CALL PDAF_print_info(11)49 CALL PDAF_print_info(11) 49 50 }}} 50 51 to the routine `finalize_pdaf`. … … 75 76 This timing display is particularly aimed at distinguishing the time spent in call-back routines from the time spent in PDAF-internal routines or PDAF-OMI internal routines. This timing information indicate those call-back routines that need particularly much time. 76 77 78 The timing information is for a single process. In the example codes, this is the process with `mype_world=0`. Without checking for `mype_world` one can let each process display its timing information. 79 77 80 Less detailed information cab be obtained using a value of 1, and more detailed information can be obtained using a value of 4 in the call to `PDAF_print_info`. 78 81