New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
ticket/0871/Review (diff) – NEMO

Changes between Version 2 and Version 3 of ticket/0871/Review


Ignore:
Timestamp:
2011-10-19T16:58:16+02:00 (13 years ago)
Author:
rblod
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ticket/0871/Review

    v2 v3  
    4848Various tests have been performed on intel with ifort compiler and IBM with xlf: 
    4949 
    50 - first without openmp : works fine for different kind of files (restart, outputs), if the size of the variable to rebuild doesn't exceed half of the RAM memory. For instance in the case of 
     50- first without OpenMP : works fine for different kind of files (restart, outputs), if the size of the variable to rebuild doesn't exceed half of the RAM memory. For instance it fails in the case of 
     51a 3D variable of dimension 300*300*50 with daily outputs during on year on a 8Gb computer. The variable size is around 4Gb, and has to be allocated twice, for the global array to be rebuilt and the sum of the local arrays.[[BR]] 
     52Note that the old rebuild is using a time loop to write the fileds record by record and save memory.  [[BR]] 
     53- with OpenMP and ifort : it fails at first and i had to declare indlimlens as SHARED. After that change, it runs, but the rebuilt fields are not correct. I had it working in commenting the nested OpenMP loops and using OpenMP only on the number of input files. [[BR]] 
    5154 
    52 a 3D variable of dimension 300*300*50 with daily outputs during  
     55- with OpenMP and xlf: it runs fine with 3D variables, 2D variables are not correct (to be re-tested by me). It also fails with big arrays 
    5356 
    5457'''Code Review''' 
     
    6467=== Review Summary === 
    6568Add summary here 
     69I don't thing OpenMP problems are major. For ifort, it may be due to the support of nested OpenMP directives n the given implementation, the 2D variables problem has tobe re-checked. 
     70I've got more concern with the memory issue, even if it's strongly related to the configuration in use. 
    6671 
    6772=== Approval for the trunk ===