sinfo -N --Format=nodehost,cpusstate,cpusload,memory,freemem,statecompact
--
You received this message because you are subscribed to the Google Groups "Nextflow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nextflow+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/nextflow.
For more options, visit https://groups.google.com/d/optout.
Hi Pietro,Could you report also the "cpu raw usage", maybe there's something odd with the formatting.p
On Fri, Feb 16, 2018 at 10:54 AM, Pietro Marchesi <pietroma...@gmail.com> wrote:
I am running a Nextflow pipeline on a Slurm cluster, and am confused as to how Nextflow computes the percentage of CPU used versus the CPU_LOAD that I get in Slurm.Monitoring the state of the nodes during execution with sinfo,sinfo -N --Format=nodehost,cpusstate,cpusload,memory,freemem,statecompact
I get that the CPU_LOAD is always quite low (around 1). If I then look at the Nextflow report, the % Allocated CPUs Used is between 1000 and 2000 for those same jobs.In the pipeline I only ask for 1 cpu per job, although on this system I get a full node allocated per job, so that is 256 cores (64 cores. 4 hw threads), so if Nextflow computes its measure based on the requested resources (instead of allocated) then this may account for at least some of the difference.Does anyone have any experience on this?Cheers,Pietro
--
You received this message because you are subscribed to the Google Groups "Nextflow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nextflow+u...@googlegroups.com.
NXF_VER=0.28.0-SNAPSHOT nextflow run ...etc
To unsubscribe from this group and stop receiving emails from it, send an email to nextflow+unsubscribe@googlegroups.com.