Allocations and compute scheduling: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 65: Line 65:


<!--T:33-->
<!--T:33-->
Nothing bad.  Your CPU or GPU allocation is a target level, i.e., a target number of CPUs or GPUs.  If you have jobs waiting to run, and competing demand is low enough, then the scheduler may allow more of your jobs to run than your target level.  The only consequence of this is that succeeding jobs of yours <i>may</i> have lower priority for a time while the scheduler prioritizes other groups which were below their target.  You are not prevented from submitting or running new jobs, and the time-average of your usage should still be close to your target, that is, your allocation.
Nothing bad.  Your CPU or GPU allocation is a target level, i.e., a target number of CPUs or GPUs.  If you have jobs waiting to run, and competing demand is low enough, then the scheduler may allow more of your jobs to run than your target level.  The only consequence of this is that succeeding jobs of yours <i>may</i> have lower priority for a time while the scheduler prioritizes other groups which were below their target.  You are not prevented from submitting or running new jobs, and the average of your usage over time should still be close to your target, that is, your allocation.


<!--T:34-->
<!--T:34-->
rsnt_translations
56,420

edits

Navigation menu