Hi Andreas,
You could define a generic consumable resource per node and have the scheduling
take account of requests for it. In principle, you could do this for say
interface_bandwidth or io_bw and try and use real numbers, but in practice
users don't know how much they need and will use and ad
I think the situation is likely to be a little different. Let’s consider a
fortran program that statically or dynamically defines large arrays. This
defines a virtual memory size – like declaring that this is the maximum amount
of memory you might use if you fill the arrays. That amount of real
Hi Emyr,
Perhaps you could be more explicit about the i/o boundedness and have jobs
request an io gres as well as compute and memory resource. You could then set
the amount of io resource per node (and maybe globally - possibly separate
iolocal and ioglobal). Then you could avoid io contention
