Reduce wallclock time and/or PE count of some tests

Aperta
  • Qualcosa non va?
#4,282 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@ekluzek ci sta già lavorando.

Dal 5/11/2026.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
fortran
Ambito
testing

Direzione di ricerca

Start with the listed aux_clm tests and their test configuration files, then inspect how each test sets PE layout and wallclock limits. Compare configured limits with the reported runtimes and try smaller layouts or shorter limits for the candidates identified. Done means the selected tests use appropriately reduced resources and still pass.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

b4b testing

A few years ago, I went through the aux_clm test list and reduced the wallclock time and/or PE count of tests to get better turnaround of the aux_clm test list. Since then, some tests have been added that have either longer-than-needed wallclock time, large PE counts, or both.

From a recent run of aux_clm on derecho, these are the tests still stuck in the queue and my suggestion for how to improve test turnaround:

Best candidates for improvement:

  • ERS_D.f19_g17.I1850Clm50BgcCrop.derecho_intel.clm-ciso_monthly_matrixcn_spinup
    • Can this be moved to lower resolution?
    • If not, then use a smaller PE layout; I believe my goal a few years ago was to have all aux_clm tests fit in 4 nodes or less to get better turnaround time (the slower run time is usually worth it for the faster turnaround time); I suggest trying 1, 2 or 4 nodes (_PS for f19_g17 gives 1 node, so that's probably a good place to start).
    • Also reduce wallclock time from 1 hour 20 min to something much smaller (currently takes 4 minutes)
  • PEM_D_Ld5.ne30_g17.I2000Clm50Bgc.derecho_intel.clm-default
    • Can this be moved to lower resolution?
    • If not, then use a smaller PE layout; I believe my goal a few years ago was to have all aux_clm tests fit in 4 nodes or less to get better turnaround time (the slower run time is usually worth it for the faster turnaround time); I suggest trying 1, 2 or 4 nodes
    • Also reduce wallclock time from 1 hour to something much smaller (currently takes 5 minutes)
  • REP_P64x2_Ld13.f10_f10_mg37.IHistClm60Bgc.derecho_intel.clm-monthly--clm-matrixcnOn_ignore_warnings
    • Reduce wallclock time from 2 hours to something like 10 minutes (currently takes 2 minutes)
  • ERP_P64x2_Ld396.f10_f10_mg37.IHistClm60Bgc.derecho_intel.clm-monthly--clm-matrixcnOn_ignore_warnings
    • Reduce wallclock time from 2 hours to something like 20 - 30 minutes (currently takes 12 minutes)

There may not be much that can be done about these:

  • ERS_Ly5_P128x1.f10_f10_mg37.IHistClm60BgcCrop.derecho_intel.clm-cropMonthOutput
    • Could reduce wallclock time slightly, from 2 hours to something like an hour or a little more (currently takes 47 minutes)
    • But there may not be much that can be done about this one
  • ERS_Ly5_P128x1.f10_f10_mg37.IHistClm60BgcCrop.derecho_intel.clm-cropMonthOutput--clm-matrixcnOn_ignore_warnings
    • Could reduce wallclock time slightly, from 2 hours to something like an hour or a little more (currently takes 52 minutes)
    • But there may not be much that can be done about this one
  • SMS_Ly2_PS.f19_g17.I2000Clm60BgcCrop.derecho_intel.clm-cropMonthOutput
    • Could reduce wallclock time slightly, from 2 hours to a little over an hour (currently takes 57 minutes)
    • But there may not be much that can be done about this one
Lingua principale
Fortran
Stelle
353
Fork
368
Merge medio
2g 15h
PR unite (30g)
12

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ESCOMP/CTSM

Tutte le issue di ESCOMP/CTSM

Issue simili

Altre issue su Testing & QA

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.