Skip to content

Many individual jobs with identical resource requirements created rather than job array #512

Description

@tardigradus

Hi,

I am not a user of pbdff but an administrator of an HPC system where it is used.

As I understand it, when used with a scheduler, the tool creates individual jobs with identical resource requirements rather than what on a system using Slurm would be called a job array. The problem with this is that it can significantly reduce the effectiveness of backfill, even to the point of essentially disabling it. Slurm can check waiting jobs to see whether gaps in the schedule can be filled with jobs that would otherwise have to wait. However, only a finite number of jobs are checked and checks on multiple jobs with the the same resource requirements are redundant. With a job array, Slurm can just check a single element of the array and then move on to the next job or job array.

It is obviously going to be a bit of a pain to implement job arrays, since I assume that PBS has something similar but different. However, if backfill does become disabled by jobs run via pbdff, HPC admins may consider penalising such jobs in order to maintain the total throughput of their system. So I hope addressing this issue will be in your interest and that of users of pbdff too.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionAsking for support or clarification

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions