From 7e6bd8089cd079417e57aa9870d6e3a165640ce6 Mon Sep 17 00:00:00 2001
From: Branislav Jansik <branislav.jansik@vsb.cz>
Date: Fri, 2 May 2025 17:03:06 +0200
Subject: [PATCH] Edit capacity-computing.md
---
docs.it4i/general/capacity-computing.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs.it4i/general/capacity-computing.md b/docs.it4i/general/capacity-computing.md
index e65ea43f..92935fb8 100644
--- a/docs.it4i/general/capacity-computing.md
+++ b/docs.it4i/general/capacity-computing.md
@@ -14,11 +14,11 @@ We **recommend** using [**Job arrays**][1] or [**HyperQueue**][2] to execute man
There are two primary scenarios:
1. Numeber of jobs < 1500, **and** the jobs are able to utilize one or more **full** nodes:
- Use [**Job arrays**][2].
+ Use [**Job arrays**][1].
The Job array allows to sumbmit and control many jobs (tasks) in one packet. Several job arrays may be sumitted.
2. Number of jobs >> 1500, **or** the jobs only utilze a **few cores/accelerators** each:
- Use [**HyperQueue**][1].
+ Use [**HyperQueue**][2].
HyperQueue can help efficiently load balance a very large number of (small) jobs amongst available computing nodes.
HyperQueue may be also used if you have dependenices among the jobs.
--
GitLab