HPCE/gitea-pages
0
0
Fork 0
Code Issues 3 Pull Requests 1 Actions Packages Projects Activity

Update docs
All checks were successful
Build and Deploy Documentation / build-and-deploy (push) Successful in 6s
Details

Browse Source
This commit is contained in:
caubet_m
2025-07-31 13:55:01 +02:00
parent c69800e4be
commit ccb69b246b
1 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
pages/merlin7/03-Slurm-General-Documentation/interactive-jobs.md
View File

@@ -10,13 +10,14 @@ permalink: /merlin7/interactive-jobs.html
### The Merlin7 'interactive' partition
On `merlin7`, is recommended to always run interactive jobs on the `interactive` partition. This partition oversubscribe
CPUs (up to 4 users can use the same CPU), and has the highest priority. In general, access to this
partition should be quick, and can be used as an extension of the login nodes.
On the **`merlin7`** cluster, it is recommended to always run interactive jobs on the **`interactive`** partition.
This partition allows CPU oversubscription (up to four users may share the same CPU) and **has the highest scheduling priority**. Access to this partition is typically quick, making it a convenient extension of the login nodes for interactive workloads.
Other interactive partitions are available on the `gmerlin7` cluster, however, the main user is for CPU access only.
Since the GPU resources are very expensive and we don't have many, please do not submit interactive allocations on GPU
nodes using GPUs unless strongly justified.
On the **`gmerlin7`** cluster, additional interactive partitions are available, but these are primarily intended for CPU-only workloads (such like compiling GPU-based software, or creating an allocation for submitting jobs to Grace-Hopper nodes).
{{site.data.alerts.warning}}
Because <b>GPU resources are scarce and expensive</b>, interactive allocations on GPU nodes that use GPUs should only be submitted when strictly necessary and well justified.
{{site.data.alerts.end}}
## Running interactive jobs