This could be done as part of a job submit plugin, but I am not aware of any work of this sort having been done. Of course if Slurm's estimate is low, then the new jobs can reach their memory limit and be killed.
Quoting Loris Bennett <[email protected]>:
Hi, We run node in mixed mode and thus have issue with users overestimating their memory requirements. We send out summaries of memory usage regularly via email, but not all users act on this information. So I was wondering whether anyone has done any work on implementing a mechanism for dynamically determining the memory needed based on the memory actually used by previous jobs? This seems like it might be feasible as a part of a submit-plugin for users who go over a threshold of a certain number of submitted jobs within a certain time interval. Any thoughts on this? Cheers, Loris -- This signature is currently under construction.
-- Morris "Moe" Jette CTO, SchedMD LLC Commercial Slurm Development and Support
