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
Since MOOSE based apps require the entire simulation to fit into memory, it would be good to have an estimate of what the memory requirements are for a given situation so that proper resources can be allocated. In some cases, when a simulation crashes with an exit code 9 (OOM), it requires a significant effort to determine if it's a resource issue or a memory issue in either MOOSE/MPI/Custom code. An estimate from MOOSE at the beginning of the solve, similar to ANSYS, of how much memory is required to fit the solve entirely in memory would help set resource allocations and help with debugging.
Design
The feature would at the beginning when printing the versions of the libraries, number of CPUs, number of DOFs, include a line about estimated memory needed.
If possible, it could even request the memory alloted to the solve and quit instead of going ahead knowing it will run out of memory.
Impact
Will help users set proper resource allocation and help with debugging out of memory errors (exit code 9).
The text was updated successfully, but these errors were encountered:
Motivation
Since MOOSE based apps require the entire simulation to fit into memory, it would be good to have an estimate of what the memory requirements are for a given situation so that proper resources can be allocated. In some cases, when a simulation crashes with an exit code 9 (OOM), it requires a significant effort to determine if it's a resource issue or a memory issue in either MOOSE/MPI/Custom code. An estimate from MOOSE at the beginning of the solve, similar to ANSYS, of how much memory is required to fit the solve entirely in memory would help set resource allocations and help with debugging.
Design
The feature would at the beginning when printing the versions of the libraries, number of CPUs, number of DOFs, include a line about estimated memory needed.
If possible, it could even request the memory alloted to the solve and quit instead of going ahead knowing it will run out of memory.
Impact
Will help users set proper resource allocation and help with debugging out of memory errors (exit code 9).
The text was updated successfully, but these errors were encountered: