<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Hi Paul,<div><br></div><div>Thank you for the explanations. Actually this was not the main point of the question asked. I think we can close the discussions. </div><div><br></div><div>The main point was: why a job is running more efficiently using sbatch than salloc.</div><div><br></div><div>Thank you all for the contributions. </div><div><br></div><div>- Mike<br><br><div dir="ltr">Sent from my iPhone</div><div dir="ltr"><br><blockquote type="cite">On Jul 5, 2023, at 12:33 PM, Paul H. Hargrove <phhargrove@lbl.gov> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr">Mike,<div><br></div><div>I think your definitions are probably in the minority on this list.</div><div><div>To be clear, I am <i>not</i> saying you (or SGE) are wrong, just that the folk here use different terms for what you are asking for.</div><div>I think of it like dialects of English where the same food might be a "cookie" or a "biscuit" depending on the local dialect.</div></div><div><br></div><div>To me, "interactive" means "keyboard interactive".</div><div><br></div><div><div>If I want the most immediate access then "immediate" is the term I use.</div><div>Fwiw, the `srun` and `salloc` commands have an `--immediate=time` option to bound how long they wait for resources.</div><div><br></div><div>It is possible to define an "immediate" or "interactive" (or any other name you may choose) QOS to ensure that interactive jobs are scheduled on a distinct partition of the cluster and/or are given higher priority in scheduling of nodes which are also used for non-interactive jobs.</div><div><br></div></div><div>I've just confirmed that LSF and PBS documentation use the term "interactive" in the same way as Slurm.</div><div><br></div><div>-Paul</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 5, 2023 at 7:06 AM Mike Mikailov <<a href="mailto:mmikailov@gmail.com">mmikailov@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thank you Loris, for the further feedback. <br>
<br>
“Reasonable” for SGE is within a few minutes, would be nice if it could be adjusted. <br>
<br>
Still interactive means the user has almost immediate access to the system, not queued. <br>
<br>
Sent from my iPhone<br>
<br>
> On Jul 5, 2023, at 9:43 AM, Loris Bennett <<a href="mailto:loris.bennett@fu-berlin.de" target="_blank">loris.bennett@fu-berlin.de</a>> wrote:<br>
> <br>
> Mike Mikailov <<a href="mailto:mmikailov@gmail.com" target="_blank">mmikailov@gmail.com</a>> writes:<br>
> <br>
>> Thank you Loris, for the further clarifications. The only question is<br>
>> who will wait forever in interactive mode? And how practical is it?<br>
>> <br>
>> Interactive mode is what its name implies - interactive, not queueing.<br>
> <br>
> To me, "interactive" is the alternative to "batch" - queueing happens<br>
> with both. Whether I submit an interactive job or a batch job, the job<br>
> can only start if the requested resources are available and the job has<br>
> a sufficiently high priority.<br>
> <br>
> If you have enough nodes, you might be able to spare some to be<br>
> essentially idle most of the time, so that jobs sent to these nodes<br>
> will, in general, start quickly. If you have a small cluster, this<br>
> might not be an option. <br>
> <br>
>> It would make more sense if the default setting for deadline would be set to a reasonable time not indefinite in Slurm. <br>
> <br>
> One person's "reasonable" may be another person's "ridiculously long".<br>
> A "reasonable time" may even vary for the same person depending on the<br>
> circumstances. If you submit an interactive job before lunch, you might<br>
> be prepared to wait longer than if the building is going to close in 30<br>
> minutes and you will have to leave. With '--deadline' you can decide<br>
> case by case.<br>
> <br>
> Cheers,<br>
> <br>
> Loris<br>
> <br>
>> Sent from my iPhone<br>
>> <br>
>>>> On Jul 5, 2023, at 1:43 AM, Loris Bennett <<a href="mailto:loris.bennett@fu-berlin.de" target="_blank">loris.bennett@fu-berlin.de</a>> wrote:<br>
>>> <br>
>>> Mike Mikailov <<a href="mailto:mmikailov@gmail.com" target="_blank">mmikailov@gmail.com</a>> writes:<br>
>>> <br>
>>>> About the last point. In the case of sbatch the jobs wait in the<br>
>>>> queue as long as it takes until the resources are available. In the<br>
>>>> case of interactive jobs<br>
>>>> (at least using Son of Grid Engine) they fail after a short time if no resources available. <br>
>>> <br>
>>> But you were referring to 'salloc' and not something SGE does. The<br>
>>> default for 'salloc' is to wait indefinitely. You can change this<br>
>>> behaviour with the option '--deadline':<br>
>>> <br>
>>> --deadline=<OPT><br>
>>> remove the job if no ending is possible before this deadline<br>
>>> (start > (deadline - time[-min])). Default is no deadline.<br>
>>> Valid time formats are:<br>
>>> HH:MM[:SS] [AM|PM]<br>
>>> MMDD[YY] or MM/DD[/YY] or MM.DD[.YY]<br>
>>> MM/DD[/YY]-HH:MM[:SS]<br>
>>> YYYY-MM-DD[THH:MM[:SS]]]<br>
>>> now[+count[seconds(default)|minutes|hours|days|weeks]]<br>
>>> <br>
>>> [snip (36 lines)]<br>
>>>> <br>
>>>> Queuing system No Yes <br>
>>>> <br>
>>>> I am not sure what you mean with the last point, since 'salloc' is also<br>
>>>> handled by the queueing system. If the resources requested are<br>
>>>> currently not available, 'salloc' will wait until they are.<br>
>>> <br>
>>> [snip (42 lines)]<br>
>>> <br>
>>> -- <br>
>>> Dr. Loris Bennett (Herr/Mr)<br>
>>> ZEDAT, Freie Universität Berlin<br>
>>> <br>
> -- <br>
> Dr. Loris Bennett (Herr/Mr)<br>
> ZEDAT, Freie Universität Berlin<br>
> <br>
<br>
</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div dir="ltr"><div style="font-family:"courier new",monospace">Paul H. Hargrove <<a href="mailto:PHHargrove@lbl.gov" target="_blank">PHHargrove@lbl.gov</a>><br>Pronouns: he, him, his<br></div><div style="font-family:"courier new",monospace">Computer Languages & Systems Software (CLaSS) Group</div><div style="font-family:"courier new",monospace">Computer Science Department</div><div style="font-family:"courier new",monospace">Lawrence Berkeley National Laboratory</div></div></div></div>
</div></blockquote></div></body></html>