You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@AGonzalezNicolas' investigation of eCLM failing on >16 JURECA nodes shows that the different MPI-settings on JSC systems have different memory and performance behavior. Wrong settings can cause failure (as with the linked issue) or constrain model performance. Knowing the optimal MPI-settings can be highly relevant for high-resolution simulations.
[jrc0477:45753:0:45753] ib_mlx5_log.c:179 Transport retry count exceeded on mlx5_0:1/IB (synd 0x15 vend 0x81 hw_synd 0/0)
This is caused by too many dropped IP packets across the MPI fabric (1, 2). I'm starting to suspect that very high resolution runs (e.g. DE009, EUR0275) that save NetCDF files in parallel mode (pio_typename = netcdf4p) is pushing the JSC MPI comm fabric to its limit. @AGonzalezNicolas it could be a good idea to benchmark what NetCDF I/O settings are apt given a particular MPI library or runtime setting.
Activity
kvrigor commentedon Sep 4, 2026
Another instance of MPI runtime error reported by @bnaz2004:
This is caused by too many dropped IP packets across the MPI fabric (1, 2). I'm starting to suspect that very high resolution runs (e.g.
DE009,EUR0275) that saveNetCDFfiles in parallel mode (pio_typename = netcdf4p) is pushing the JSC MPI comm fabric to its limit. @AGonzalezNicolas it could be a good idea to benchmark what NetCDF I/O settings are apt given a particular MPI library or runtime setting.Updated eCLM to rc-0.1
Updated eCLM to `rc-0.1` (#151)