From 62a9d18ffb3ec037f3e93767681654fac8729271 Mon Sep 17 00:00:00 2001 From: stdweird Date: Mon, 23 Oct 2023 15:10:07 +0200 Subject: [PATCH] clarify the possible OMP_PROC_BIND issue --- mkdocs/docs/HPC/only/gent/2023/shinx.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/mkdocs/docs/HPC/only/gent/2023/shinx.md b/mkdocs/docs/HPC/only/gent/2023/shinx.md index fe713dab289..939bb77c857 100644 --- a/mkdocs/docs/HPC/only/gent/2023/shinx.md +++ b/mkdocs/docs/HPC/only/gent/2023/shinx.md @@ -69,7 +69,11 @@ optimizations (like GCC's `-march=native`, or Intel compiler's `-xHost`) might s ### Other remarks * Possible issues with `OpenMP` thread pinning: we have seen, especially on `Tier-1 dodrio` cluster, that in certain cases -thread pinning occurs that also affects +thread pinning is invoked where it is not expected. Typical symptom is that all the processes that are started are pinned +to a single core. Always report this issue when it occurs. +You can try yourself to mitigate this by setting `export OMP_PROC_BIND=false`, but always report it so we can keep track of this problem. +It is not recommended to always set this workaround, only for the specific tools that are affected. + ---