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.
#2010 (HPC-03_Mocavero_globcomm) – NEMO

Opened 6 years ago

Last modified 2 years ago

#2010 closed Task

HPC-03_Mocavero_globcomm — at Version 8

Reported by: mocavero Owned by: francesca
Priority: high Milestone: 2018 release-4.0
Component: OCE Version: trunk
Severity: minor Keywords: OPA v4.0
Cc:

Description (last modified by francesca)

Context

Reducing MPI communications overhead by conditioning or removing some global communications

Implementation plan

  1. two glob_sum can be conditioned during the freshwater budget control (sbc_fwb routine)
  2. a glob_sum is executed at each time step during the computation of the carbon flux (p4z_flx routine) even if it is used only at output and restart writing time. It can be conditioned.
  3. three glob_sum are used to compute the loss of biogenic silicon (p4z_sed routine). One of them can be removed because the result is not used
  4. four glob_sum are used during the correction to the artificial negative concentrations (trc_rad_sms routine). Two of them can be conditioned depending on the result of the other ones
  5. a global communication (mpp_max) is used for the convergence test in the ice_dyn_rhg_evp routine. It can be removed because the result is not used
  6. a global communication (mpp_max) is used to stop the control loop on the flux delimiters (wetting/drying routines). The control frequency could be reduced

Commit History (2)

ChangesetAuthorTimeChangeLog
10288francesca2018-11-07T18:25:49+01:00

reduce global communications, see #2010

9871mocavero2018-07-04T10:36:15+02:00

Create HPC-03 branch - ticket #2010

Change History (8)

comment:1 Changed 6 years ago by clevy

  • Milestone changed from 2018 WP to 2018 release-4.0

comment:2 Changed 6 years ago by mocavero

  • wp_comment set to Need to update the analysis performed on global communications on the latest version of the code (already started). Removing the useless global communications

comment:3 Changed 6 years ago by nemo

  • Status changed from new to assigned

comment:4 Changed 6 years ago by mocavero

In 9871:

Error: Failed to load processor CommitTicketReference
No macro or processor named 'CommitTicketReference' found

comment:5 Changed 6 years ago by mocavero

  • wp_comment changed from Need to update the analysis performed on global communications on the latest version of the code (already started). Removing the useless global communications to The analysis on global communications has been updated on the new trunk and the development branch has been created. The wiki will be updated with the list of communications that can be removed or merged (multiple communication) and the ticket will be closed by the end of this year.

comment:6 Changed 6 years ago by francesca

  • Description modified (diff)
  • Owner changed from mocavero to francesca
  • wp_comment changed from The analysis on global communications has been updated on the new trunk and the development branch has been created. The wiki will be updated with the list of communications that can be removed or merged (multiple communication) and the ticket will be closed by the end of this year. to The analysis on global communications has been updated on the trunk and the development branch has been created. A list of communications that can be safely removed is reported in the "Implementation plan" section. They will be removed in the development branch and the ticket will be closed by the end of this year.

comment:7 Changed 5 years ago by francesca

In 10288:

Error: Failed to load processor CommitTicketReference
No macro or processor named 'CommitTicketReference' found

comment:8 Changed 5 years ago by francesca

  • wp_comment changed from The analysis on global communications has been updated on the trunk and the development branch has been created. A list of communications that can be safely removed is reported in the "Implementation plan" section. They will be removed in the development branch and the ticket will be closed by the end of this year. to The analysis on global communications has been updated on the trunk and the development branch has been created. A list of communications that can be safely removed is reported in the "Implementation plan" section. They will be removed in the development branch and the ticket will be closed by the end of this year. The development branch has been aligned to the current version of the trunk (trunk@rev10279). Global communications listed in the implementation plan section (points 1-5) have been removed.
Note: See TracTickets for help on using tickets.