runtime

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
runtime [2021/09/14 14:47]
jrutte02 removed
— (current)
Line 1: Line 1:
-====== Specifying Runtime ====== 
- 
-Requesting runtime is straightforward: The ''-t'' or ''--time'' flag can be used in ''srun''/''salloc'' and ''sbatch''  alike: 
- 
-<code bash> 
-$ srun --time <time reservation> 
-</code> 
- 
-or within a script 
-<code bash> 
-#SBATCH -t <time reservation> 
-</code> 
-where ''<time reservation>'' can be any of the acceptable time formats ''minutes'', ''minutes:seconds'', ''hours:minutes:seconds'', ''days-hours'', ''days-hours:minutes'' and ''days-hours:minutes:seconds'' 
- 
-Time resolution is one minute and second values are rounded up to the next minute. A time limit of zero requests that no time limit be imposed, meaning that the maximum runtime of the [[partitions]] will be used. 
- 
-===== Signals ===== 
- 
-Slurm does not send signals if not requested. You can request a specific signal with ''--signal'' either to ''srun'' or ''sbatch'' from within a script. The flag can be used like ''--signal=<sig_num>[@<sig_time>]'': When a job is within ''sig_time'' seconds of its end time,  then the signal ''sig_num'' is sended. If a sig_num is specified without any sig_time, the default time will 60 seconds. Due to the resolution of event handling by Slurm, the signal may be sent up to 60 seconds earlier than specified. 
- 
-An example would be 
- 
-<code bash> 
-$ sbatch --signal=SIGUSR2@600 ... 
-</code> 
-here, the signal ''SIGUSR2'' is send to the application ten minutes before hitting the walltime of the job. Note once more that the slurm documentation states that there is a uncertainty of up to 1 minute. 
- 
- 
  
  • runtime.1631623674.txt.gz
  • Last modified: 2021/09/14 14:47
  • by jrutte02