Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| doku:runtime [2014/05/28 10:03] – ir | doku:runtime [2021/05/13 17:44] (current) – removed goldenberg | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Specifying the maximum runtime ====== | ||
| - | The specification of the maximum runtime may render the job execution faster by reducing the time waiting in the queue. | ||
| - | === Slot reservation for large jobs === | ||
| - | In order to ensure that large jobs are able to run on the cluster and in order to avoid blocking by many smaller jobs,the queueing system used on the VSC enables for the **reservation of slots**. | ||
| - | This feature is **automatically** activated **for any jobs requiring 16 or more slots**. | ||
| - | |||
| - | The down side of this feature is that a certain amount of resources is unused until the total amount of slots for a queued large job is available. | ||
| - | === Faster scheduling by backfilling === | ||
| - | In the meantime waiting for a large job to be scheduled, idle resources could be used by smaller jobs. By conserving the priorities of the jobs on top of the list, only jobs can pass which have a maximum runtime shorter than the expected time needed to free the total amount of slots requested by the large job. | ||
| - | |||
| - | Users can profit from this process called **backfilling** by adding this on top of the job submission script: | ||
| - | < | ||
| - | #$ -l h_rt=01: | ||
| - | Here, h_rt means "hard runtime" | ||
| - | |||
| - | We hope that you are able and **willing to utilize this feature** as it would **save a lot of electricity** and greatly **reduce the time your jobs spend in the queue**!\\ | ||
| - | Please put our precious computing time to use as best as you can. | ||