search

OleHolmNielsen / Slurm_tools

My tools for the Slurm HPC workload manager
GNU General Public License v3.0
442 stars 96 forks source link

free vs. available memory #13

Closed bernstei closed 2 years ago

bernstei commented 3 years ago

Is there any way for pestat to report on what the free command calls "available" rather than "free"? Since "free" includes usage for file caching, I don't find it the most useful for figuring out if a node is actually overloaded.

bernstei commented 3 years ago

Looking over sinfo -O I suspect the answer is no, so feel free to close this issue if you don't think there's a reasonable solution. What do you think about computing Memory - AllocMem?

[edited: just checked, and AllocMem doesn't behave like I'd expect either]

OleHolmNielsen commented 3 years ago

That's a good point with memory taken for file caching. IMHO it's the free memory that really counts for what remains available to the user jobs. Maybe you can discuss the relative merits of FreeMem vs. (Memory - AllocMem). Could you ask the Slurm users list for what's most appropriate and useful? Thanks, Ole