QueuePolicies

From HLRS Dgrid
Jump to: navigation, search

Back to Batch System


Jobs are submitted by the user to the queue 'user'. The declaration together with the qsub command is optional.

 qsub -q user <...>

The further processing is done according to the requested amount of resources.

Job classes for the bwGRiD-Cluster

Different job classes are available for efficient resource usage. In the following the definition for each job class is given. In general jobs with a Duration up to 24 hours and half of the available resources can be submitted. For larger job different restrictions are in place respectively you have to consult the project team.

All submittion is only possible to the default queue "user". The queueing system will then sort the jobs in the proper queu according to time and resource consumption in yout job description.

All jobs without a specific duration (walltime) will be set to the default of 20 Minutes.

Last status update: Nov. 15th 2009

bw-test

This class is for tests with restricted resources needs. The jobs in this class are expected to deliver results after very short time and shall allow interactive work.

 bw-test       Minimum      Maximum      Standard
 ------------------------------------------------
 walltime:                  01:00:00     
 nodes:                     4             
 ncpus:                     32            
 avail. nodes: 11 (n110401-n110414)
 ------------------------------------------------

bw-single

This class is only jobs which uses only one node.

 bw-single     Minimum      Maximum      Standard
 ------------------------------------------------
 walltime:     00:01:00     24:00:00
 nodes:        1            1
 ncpus:        1            8
 avail. nodes: 53
 ------------------------------------------------

bw-*multi

This class is for parallel applications.

 bw-vsmulti    Minimum      Maximum      Standard
 ------------------------------------------------
 walltime:     00:01:00     4:00:00
 nodes:                      4
 ncpus:                     32
 avail. nodes: 498
 ------------------------------------------------
 bw-smulti     Minimum      Maximum      Standard
 ------------------------------------------------
 walltime:     00:01:00     12:00:00
 nodes:                      210
 ncpus:                     1680
 avail. nodes: 402
 ------------------------------------------------
 bw-multi      Minimum      Maximum      Standard
 ------------------------------------------------
 walltime:     00:01:00     24:00:00
 nodes:                      210
 ncpus:                     1680
 avail. nodes: 347
 ------------------------------------------------

bw-giant

If you need more resources than available within the given queues, please contact us.

Jobs in this class will be accumulated by the system and started manually at a proper point in time. You have to anticipate that it will take up to several days to start these jobs. This queue isn't available all the time.

Maximum allowed jobs for each class

The number of jobs for each user in the different job classes is restricted to the following. If you reach this number you can submit further jobs when prior jobs have ended.

Job-class      Max. number       (Max. with waiting
               of jobs           queue 'user')
---------------------------------------------
bw-test          5                15
bw-single       25                35
bw-multi        25                35
bw-smulti       25                35
bw-vsmulti      25                35
---------------------------------------------

If more jobs are submitted than allowed for one job class the odd ones will be placed in the Dispatcher queue 'user' and will move up in the proper queue after jobs from this user in the corresponding queue have ended. The waiting queue for each user will take up to 10 jobs. With this it is possible to submit job ahead.