On Mon, Jan 24, 2022 at 01:17:30PM -0600, Tom Harvill wrote:
>
>
> Hello,
>
> We use a 'fair share' feature of our scheduler (SLURM) and have our decay
> half-life (the time needed for priority penalty to halve) set to 30 days.
> Our maximum job runtime is 7 days. I'm wondering what others use
On 1/24/22 11:17 am, Tom Harvill wrote:
We use a 'fair share' feature of our scheduler (SLURM) and have our
decay half-life (the time needed for priority penalty to halve) set to
30 days. Our maximum job runtime is 7 days. I'm wondering what others
use, please let me know if you can spare a
Our half life is 30 days and we keep 6 months of data in our database.
The maximum run time depends on partition. We have about 100 of them.
Some with unlimited. Our main public partition has a maximum runtime of
7 days. See:
https://docs.rc.fas.harvard.edu/kb/running-jobs/#Slurm_partition
Thank you Mr. Edmon,
The link you provided is comprehensive and well-written. However, I
don't see the scheduler configured half-life time length. Do you know
what it is? And what is your clusters' maximum job runtime?
On 1/24/22 1:47 PM, Paul Edmon via Beowulf wrote:
Here is our fairshare
Here is our fairshare policy doc:
https://docs.rc.fas.harvard.edu/kb/fairshare/ We use the classic
fairshare here.
-Paul Edmon-
On 1/24/2022 2:17 PM, Tom Harvill wrote:
Hello,
We use a 'fair share' feature of our scheduler (SLURM) and have our
decay half-life (the time needed for priorit
Hello,
We use a 'fair share' feature of our scheduler (SLURM) and have our
decay half-life (the time needed for priority penalty to halve) set to
30 days. Our maximum job runtime is 7 days. I'm wondering what others
use, please let me know if you can spare a minute. Thank you!
Tom
Tom
