38,760
edits
(Importing a new version from external source) |
(Importing a new version from external source) |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
The | The runtime you choose should be significantly larger than the average runtime of an individual case, ideally by a factor of 100 or more. | ||
It must definitely be larger than the longest | It must definitely be larger than the longest runtime you expect for an individual case. | ||
On the other hand it should not be too large; say, no more than 3 days. | On the other hand it should not be too large; say, no more than 3 days. | ||
The longer a job's | The longer a job's runtime is, the longer it will usually wait to be scheduled. | ||
On Alliance general-purpose clusters, a good choice would be 12h or 24h due to [[Job_scheduling_policies#Time_limits|scheduling policies]]. | On Alliance general-purpose clusters, a good choice would be 12h or 24h due to [[Job_scheduling_policies#Time_limits|scheduling policies]]. | ||
Once you have settled on a | Once you have settled on a runtime, divide the total number of CPU-hours by the runtime you have chosen (in hours) to get the required number of metajobs. | ||
Round up this number to the next integer. | Round up this number to the next integer. |