Changes between Version 1 and Version 2 of Working Groups/HPC/Mins_2020_07_28


Ignore:
Timestamp:
2020-07-28T18:03:57+02:00 (3 months ago)
Author:
epico
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Working Groups/HPC/Mins_2020_07_28

    v1 v2  
    1616 
    1717- I.Epicoco introduces the meeting underlighting the role of the NEMO HPC-WG.  
    18   + The HPC-WG should be more proactive in suggesting the HPC development actions for the next years moving and following the guidelines depicted in the NEMO Development Strategy Document 
    19   + The HPC-WG should evaluate, assess and discuss about the matureness and effectiveness of the currently developing branches giving some feedback to the NEMO ST.  
    20   + The HPC-WG should investigate about new HPC methods, solutions and optimizations that can be introduced in NEMO HPC development strategy. 
     18  * The HPC-WG should be more proactive in suggesting the HPC development actions for the next years moving and following the guidelines depicted in the NEMO Development Strategy Document 
     19  * The HPC-WG should evaluate, assess and discuss about the matureness and effectiveness of the currently developing branches giving some feedback to the NEMO ST.  
     20  * The HPC-WG should investigate about new HPC methods, solutions and optimizations that can be introduced in NEMO HPC development strategy. 
    2121 
    2222- Comments regarding mixed precision and its status 
    23   + interesting are the first thoughts depicted by O.Tinto regarding the guidelines a NEMO developer should follow when facing up with the mixed precision code 
    24   + I.Epicoco proposed to execute the performance assessment also on other HPC architectures; O.Tinto confirmed that an automatic procedure is already under development at BSC for automatic performance evaluation, it could be shared to make the tests easier.  
     23  * interesting are the first thoughts depicted by O.Tinto regarding the guidelines a NEMO developer should follow when facing up with the mixed precision code 
     24  * I.Epicoco proposed to execute the performance assessment also on other HPC architectures; O.Tinto confirmed that an automatic procedure is already under development at BSC for automatic performance evaluation, it could be shared to make the tests easier.  
    2525 
    2626- Comments regarding the XIOS benchmarking 
    27   + quite impressive the detailed test plan presented by M.Acosta to assess the XIOS performance with IFS 
    28   + as partial conclusion after the first evaluation of XIOS with NEMO ORCA36 given by M.Castrillo is that XIOS 2.5 needs still further investigations in order to fully exploit all of its functionalities. At the moment XIOS suffers of a high memory footprint. I.Epicoco agrees on that. 
    29   + K.Mogensen suggested to use XIOS by saving each variable to a different file, this should tradeoff between the advantage given by writing of different and independent files with the advantage of having the whole domain of a variable saved in a file. 
     27  * quite impressive the detailed test plan presented by M.Acosta to assess the XIOS performance with IFS 
     28  * as partial conclusion after the first evaluation of XIOS with NEMO ORCA36 given by M.Castrillo is that XIOS 2.5 needs still further investigations in order to fully exploit all of its functionalities. At the moment XIOS suffers of a high memory footprint. I.Epicoco agrees on that. 
     29  * K.Mogensen suggested to use XIOS by saving each variable to a different file, this should tradeoff between the advantage given by writing of different and independent files with the advantage of having the whole domain of a variable saved in a file.