Search

link to homepage

Institute for Advanced Simulation (IAS)

Navigation and service


Job Classes and Scheduling

LoadLeveler is configured with the following limits and classes (defining the number of midplanes to be used and ordered by descending priority):

Class NameNodesMax. RuntimeDefault RuntimeMax. Jobs per UserRunning on BasePartition
m14465537 - 7372824:00:0006:00:00-on demand only
m12832769 - 6553624:00:0006:00:00-on demand only
m06424577 - 3276824:00:0006:00:00-all
m04816385 - 2457624:00:0006:00:00-all
m0328193 - 1638424:00:0006:00:00-all
m0164097- 819224:00:0006:00:00-all
m008 2049 - 409624:00:0006:00:00-all
m004 1025 - 204824:00:0006:00:00-all
m002513 - 1024 24:00:0006:00:00-all
m001257 - 512 24:00:0006:00:00-all
small32 - 25600:30:0000:30:002R87-M0, R87-M1
nocsmall32 - 25600:30:0000:30:001R87-M0, R87-M1

The job class is automatically enforced by LoadLeveler depending on the size of a job. The scheduler prioritizes the idle jobs regarding to the class priority, the job submission time, the user's quota, and the number of jobs a user has already running.

The scheduler runs the job with the highest priority if the necessary resources are available. If the requested resources are not yet available the scheduler uses a backfilling strategy to run lower priority jobs with short duration on available resources as long as doing so will not delay the starting of the highest priority job. The chance for a job to get scheduled increases the smaller the wall clock limit is.


Servicemeu

Homepage