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
Apologies if this is already addressed somewhere else, and/or if not relevant.
As part of looking into a memory issue in RunIII2024Summer24DRPremix, I stumbled on the fact that in a stepchain setup, if one of the early step is interrupted by the memory watch-guard, the rest of the steps are ran regardless, and to my knowledge, since the job is marked as failed, any of the output will be discarded anyways.
Would it be better to stop the job at the step that was interrupted and not waste the cpu running things that will be thrown away ?
The text was updated successfully, but these errors were encountered:
Apologies if this is already addressed somewhere else, and/or if not relevant.
As part of looking into a memory issue in RunIII2024Summer24DRPremix, I stumbled on the fact that in a stepchain setup, if one of the early step is interrupted by the memory watch-guard, the rest of the steps are ran regardless, and to my knowledge, since the job is marked as failed, any of the output will be discarded anyways.
Would it be better to stop the job at the step that was interrupted and not waste the cpu running things that will be thrown away ?
The text was updated successfully, but these errors were encountered: