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.
WorkingGroups/HPC/Mins_2016_09_30 (diff) – NEMO

Changes between Version 1 and Version 2 of WorkingGroups/HPC/Mins_2016_09_30


Ignore:
Timestamp:
2016-11-11T09:04:49+01:00 (7 years ago)
Author:
mikebell
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkingGroups/HPC/Mins_2016_09_30

    v1 v2  
    1818Sylvia and Cyril have performed tests (i) executing the GYRE sequential code on a single core of the node; (ii) executing more than one instance of this sequential code concurrently on the same node (each one on a different core); and have compared the execution times of the two tests. Results show a gap between the two tests (~20% on IB node, ~ 25% on SB node) and reinforce the idea that we should analyze the performance of the code by executing more instances of the sequential code (which allows to avoid the parallelization overhead, but allows to simulate the concurrency among the parallel processes) 
    1919 
    20 Action: Tim to check which routines GYRE uses (to check they cover the important ones) and to consider whether a configuration with a sloping bathymetry should be used.    
     20'''Action''': Tim to check which routines GYRE uses (to check they cover the important ones) and to consider whether a configuration with a sloping bathymetry should be used.    
    2121  
    2222 
     
    6262Jean-Marc Molines did a lot of work assessing and improving the computational performance of the Grenoble 1NM north Atlantic NEMO configuration. IO bottle-necks were a particular issue.  
    6363 
    64 Action: Julien to circulate the reports on performance testing of the Grenoble 1NM north Atlantic NEMO configuration.   
     64'''Action''': Julien to circulate the reports on performance testing of the Grenoble 1NM north Atlantic NEMO configuration.   
    6565 
    6666