Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found

Target

Select target project
  • zih/hpcsupport/hpc-compendium
  • okhrin--tu-dresden.de/hpc-compendium
  • lama722b--tu-dresden.de/hpc-compendium
  • siat527e--tu-dresden.de/hpc-compendium
  • jupe958c--tu-dresden.de/hpc-compendium
  • best913c--tu-dresden.de/hpc-compendium
  • yge-at-tu-dresden.de/hpc-compendium
7 results
Show changes
Commits on Source (3)
......@@ -89,3 +89,14 @@ additional threads using the Slurm option `--hint=multithread` or by setting the
variable `SLURM_HINT=multithread`. Besides the usage of the threads to speed up the computations,
the memory of the other threads is allocated implicitly, too, and you will always get
`Memory per Core`*`number of threads` as memory pledge.
## Guidelines for Fair and Proportional Resource Allocation
In shared computational environments, efficient and fair use of resources is essential to
ensure that all users can benefit from the system. To achieve this, it is critical to allocate
resources — such as CPUs, GPUs, and memory—proportionally to your actual needs.
For example, if you request only a single GPU from a node, you should adjust your memory and CPU
allocations accordingly, rather than consuming disproportionate portions of
the node’s total resources. This approach prevents resource bottlenecks
where underused components block other jobs from running,
resulting in wasted capacity and delayed workflows.