From 8a5af2a24ee7806282d546a8b918a768e236dc13 Mon Sep 17 00:00:00 2001
From: Renato Alves <alves.rjc@gmail.com>
Date: Fri, 21 Apr 2017 00:20:51 +0200
Subject: [PATCH] BUG Revert back to --cpus-per-task with SLURM

Using --ntasks actually causes srun to spawn that many tasks.
So @5 with -c 10 actually ran 50!! jobs.

One extra feature from using --cpus-per-task is that each thread gets
pinned to a different CPU-thread on different CPU alignments.
Probably the best for that little extra performance gain.
---
 bin/submitjob | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bin/submitjob b/bin/submitjob
index d99a2fc..7755800 100755
--- a/bin/submitjob
+++ b/bin/submitjob
@@ -223,7 +223,7 @@ slurm_submit() {
 cat << EOF | ${LOCALCMD}
 #!/usr/bin/env bash
 #SBATCH --array=${JOB_COUNT}
-#SBATCH --ntasks=${CORES}
+#SBATCH --cpus-per-task=${CORES}
 #SBATCH -N ${NODES}
 #SBATCH --mem-per-cpu=${MEM}M
 #SBATCH -o ${LOGFILE}
-- 
GitLab