Hello,
That is some feedback and questions about Resource Pools feature in SP2. I'm evaluating it now and it doesn't work as I expect. We have a cluster with thousands of jobs, each job is 1 core job with 1 task, and let's say 2 resource pools that divide all cores
as 50/50%. So if we have 200 cores, each pool is 100 cores.
1. It is mentioned in documentation that if one group underutilize its resources, other groups can use them, but that is not happening on our cluster. If one group submits thousands of jobs they all still run on 100 cores even if other 100 cores are idle.
I understand that it probably can take some time for system to understand that part of cores is underutilized, but I waited for hours and it didn't happen.
2. If the scheduling mode is set to Queued and we have 500 jobs of one group in the queue and then 50 jobs of other group they still will be started in the same order as they are in the queue, however I expect that jobs of second group should be started
as soon as cores of they pool are released. To do it I had to switch to Balanced scheduling mode but even in that case jobs of second group sometimes sit in the queue even if there is a free space in their pool. To fix it I had to rise the priority of
second group jobs.
3. When all cluster cores are busy the pending message for the job is "Not enough available resources", but when only resource pool for this job is full but other cores are available, the message is the same. I have a suggestion to distinguish such situations
and in the latter case write something like "Resource pool *** is full" to understand more correclty why the job is pending.
It seems to me that Resource Pools are not working well or not intended to work when each computational instance is separate job, actually I'm thinking about creating cumulative jobs with multiple computational instances as tasks to move computations from
'job level' to 'task level'. Will I benefit from this change?
