... | @@ -4,8 +4,8 @@ |
... | @@ -4,8 +4,8 @@ |
|
To execute non-interactive work on Pyrene, users can request resources from the cluster computing nodes by submitting batch jobs.
|
|
To execute non-interactive work on Pyrene, users can request resources from the cluster computing nodes by submitting batch jobs.
|
|
|
|
|
|
The [Slurm](https://slurm.schedmd.com) scheduler manages the resource allocations for submitted batch jobs on Pyrene:
|
|
The [Slurm](https://slurm.schedmd.com) scheduler manages the resource allocations for submitted batch jobs on Pyrene:
|
|
* The cluster nodes are put in **partitions**. Each partition allows characterized by . Each partition corresponds to different characteristics
|
|
* The cluster nodes are put in **partitions**, depending on their hardware characteristics and the policy defined to used them.
|
|
* Partition are accessible by **accounts**, representing group of users granted with some permissions.
|
|
* Partitions are accessible by **accounts**, representing group of users granted with some permissions.
|
|
|
|
|
|
A resource allocation must specify a partition, an account, and other parameters such as the maximal execution time, the number of cores and the maximal used memory of the job. These Slurm parameters are written in **job scripts** and submitted to Slurm with the following command:
|
|
A resource allocation must specify a partition, an account, and other parameters such as the maximal execution time, the number of cores and the maximal used memory of the job. These Slurm parameters are written in **job scripts** and submitted to Slurm with the following command:
|
|
```
|
|
```
|
... | | ... | |