WIP: schedulers #47
WIP: schedulers #47
Conversation
|
|
||
| - | ||
|
|
||
| # Working interactively |
There was a problem hiding this comment.
By "interactively" here, are we referring to those special confgurations many HPC systems have where users are often allowed to acquire a tiny allocation of the machine and run jobs there in the same way they might run jobs at the shell prompt? Or, are we really only using "interactively" as a adjective for those kinds of batch job submission cases where the job is extremely short running and the queue is empty enough such that the batch system is able to schedule and run the job so quickly it feels interactive to the user?
There was a problem hiding this comment.
we are referring to the former case, the situation where the user can get book an interactive session and run jobs on a compute node from the command line. We know that this isn't an option at many sites, and the plan was to make this section straightforward to leave out. But we wanted to keep it there for those sites where it's possible since it's a smaller conceptual step to go from own laptop to interactive node on cluster, rather than directly to batch script
There was a problem hiding this comment.
or what do you think? I'm unaware of the statistics on this, slurm is configured with this interactive option on most sites in Sweden, but I don't know how it looks globally
first steps in merging hpc-in-a-day and hpc-intro. Not ready to merge yet!