[Documentation] Explain advanced scheduling features in flux
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 77
- Forks
- 7
- Avg merge
- 10h 32m
- Merged PRs (30d)
- 12
Description
Example script used in the exascale project:
#!/bin/bash
#SBATCH --qos=debug
#SBATCH --time=02:00:00
#SBATCH --chdir=/ccs/home/janssen/pyiron/projects/2023-09-24-dftfe-current
#SBATCH --get-user-env=L
#SBATCH --nodes=100
srun --cpus-per-task=56 flux start -o,--config-path=./ python test_queue_v10.py
And then in the working directory, we place the sched-fluxion-qmanager.toml file to configure the scheduling behavior of flux:
[sched-fluxion-resource]
match-policy = "lonode"
More details about the different scheduling policies are available in the flux documentation:
https://flux-framework.readthedocs.io/projects/flux-sched/en/latest/man5/flux-config-sched-fluxion-resource.html#resource-match-policies
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the provided Slurm script, the sched-fluxion-qmanager.toml example, and the linked Flux resource match-policy documentation. Add project documentation explaining how to configure and use the advanced scheduling policies, including the example commands and configuration; done means a newcomer can follow the example and understand the available policies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, python
- Domain
- documentation, hpc
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100