From b3fb0cc72dd4c7baa583b34040e827e43858fbd3 Mon Sep 17 00:00:00 2001
From: Branislav Jansik <branislav.jansik@vsb.cz>
Date: Fri, 2 May 2025 17:04:53 +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 92935fb8..80e5a539 100644
--- a/docs.it4i/general/capacity-computing.md
+++ b/docs.it4i/general/capacity-computing.md
@@ -15,11 +15,11 @@ 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**][1].
- The Job array allows to sumbmit and control many jobs (tasks) in one packet. Several job arrays may be sumitted.
+ The Job array allows to sumbmit and control up to 1500 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**][2].
- HyperQueue can help efficiently load balance a very large number of (small) jobs amongst available computing nodes.
+ HyperQueue can help efficiently load balance a very large number of jobs (tasks) amongst available computing nodes.
HyperQueue may be also used if you have dependenices among the jobs.
--
GitLab