A text-based user interface (TUI) for the Slurm Workload Manager, which provides a convenient way to manage your cluster jobs.
turm accepts the same options as squeue (see man squeue). Use turm --help to get a list of all available options.
turm is available on PyPI and crates.io:
# With pip.
pip install turm
# With pipx.
pipx install turm
# With cargo.
cargo install turmThe release page also contains precompiled binaries for Linux.
In your .bashrc, add the following line:
eval "$(turm completion bash)"In your .zshrc, add the following line:
eval "$(turm completion zsh)"In your config.fish or in a separate completions/turm.fish file, add the following line:
turm completion fish | sourceturm obtains information about jobs by parsing the output of squeue.
The reason for this is that squeue is available on all Slurm clusters, and running it periodically is not too expensive for the Slurm controller ( particularly when filtering by user).
In contrast, Slurm's C API is unstable, and Slurm's REST API is not always available and can be costly for the Slurm controller.
Another advantage is that we get free support for the exact same CLI flags as squeue, which users are already familiar with, for filtering and sorting the jobs.
TL;DR: turm ≈ watch -n2 squeue + tail -f slurm-log.out
Special care has been taken to ensure that turm is as lightweight as possible in terms of its impact on the Slurm controller and its file I/O operations.
The job queue is updated every two seconds by running squeue.
When there are many jobs in the queue, it is advisable to specify a single user to reduce the load on the Slurm controller (see squeue --user).
turm updates the currently displayed log file on every inotify modify notification, and it only reads the newly appended lines after the initial read.
However, since inotify notifications are not supported for remote file systems, such as NFS, turm also polls the file for newly appended bytes every two seconds.