Interactive jobs¶
One can work on a compute node interactively by running the interactivejobs
command.
When you run the interactivejobs
command:
- The scheduling system puts your request in the queue, waiting for resources to become available.
- You wait for the job to start.
- The scheduling system starts your job on a suitable compute node, and reserves the amount of memory and CPU cores you requested.
- You are automatically logged in to the compute node and can start working.
If your interactive session has not started after 30 seconds, The interactive session might not start immediately, this is may happen because all the resources on the system are probably already in use and you will have to wait in the queue.
Tip
You can use the devel QoS for short interactive sessions to check if your code/simulations runs.
Example interactive session:
interactivejobs -N 1 -p zen3_0512 --qos zen3_0512 --exclusive -t 1:00:00
In this example we request one whole node in the zen3_0512 partition and QOS for a whole hour.
Warning
End your interactive session by typing “exit”. In this way resources are released and become available to other users.
Note
the “interactive” command takes the same options as “sbatch”, so you can read the sbatch man page to find out all the options that can be used. The most common ones are:
salloc¶
Actually, the interactivejobs
command is a convenient wrapper around salloc. You can still use salloc if you want, but remember you need to ssh to the allocated compute node and then scancel
the job.
Example:
salloc -N 2 --qos=skylake_0096_devel --partition=skylake_0096