Hi All,
additionally write...
I changed the CPUFreq driver from intel_pstate to acpi-cpufreq.
The result was the same for intel_pstate.
Set 'CpuFreqGovernors' in slurm.conf.
# scontrol show config | grep CpuFreqGovernors
CpuFreqGovernors= Conservative,Performance,PowerSave,OnDemand,User
Hi all,
I am checking the --cpu-freq option of the sbatch command.
The CPU frequency of the target node is as follows.
# cpupower frequency-info
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coord
(most likely in the next year). My reaction is that Slurm very rarely
provides an estimated start time for a job. I understand that this is not
possible for jobs on hold and dependent jobs.
it's also not possible if both running and queued jobs
lack definite termination times; do yours?
my un
Hello.,
I have just started to take a look at Slurm v19* with a view to an upgrade
(most likely in the next year). My reaction is that Slurm very rarely provides
an estimated start time for a job. I understand that this is not possible for
jobs on hold and dependent jobs. On the other hand I've
Thanks for your comment.
I understood as follows.
In the case of a typical Linux cluster, 'Batchhost' would be the compute node
zero of the allocation.
* From BatchHost at https://slurm.schedmd.com/squeue.html
Therefore, it is not necessary to specify the '--batch' option.
Regards,
Tomo
Espen Tangen writes:
> Hi all, I need a bullet proof way of checking the setting of the
> OverSubscribe parameter from within a runscript.
Perhaps
squeue -o %h -j $SLURM_JOB_ID
is what you are looking for. According to squeue(1):
%hCan the compute resources allocated to
