Skip to content

GitLab

Une MAJ de sécurité est nécessaire sur notre version actuelle. Elle sera effectuée lundi 02/08 entre 12h30 et 13h. L'interruption de service devrait durer quelques minutes (probablement moins de 5 minutes).

Open
Created by MERCIER Michael@mmercierOwner

no-shed option is not working as expected

The --no-shed CLI option documentation reads:

If set, the jobs in the workloads are
computed one by one, one after the other,
without scheduler nor Redis.

But currently, all the jobs launch at time 0 and share the resources.

I've made some changes to make the jobs start at their submission time and not before, but we still have resource sharing and all the jobs are placed on the first hosts and not dispatched on the resources or queued.

The question is what we do? The no-sched-fix branch contains my patch and this is the behavior I wanted bu maybe we should consider to have multiple very simple policies in argument to the no-shed option...

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information