Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
wiki:coupling_oarsh_with_gnu_parallel_to_mimic_salloc_srun [2020/03/03 13:15] – ↷ Page name changed from wiki:coupling_oarsh_with_gnu_parallel_to_mimic_salloc_sbatch to wiki:coupling_oarsh_with_gnu_parallel_to_mimic_salloc_srun neyronwiki:coupling_oarsh_with_gnu_parallel_to_mimic_salloc_srun [2020/04/02 11:52] – [Run parallel] neyron
Line 8: Line 8:
  
 ===== PoC with cores ===== ===== PoC with cores =====
 +PoC in [[oar-docker]]
 ==== Create a job with 2 nodes (and all their cores, here 4) ==== ==== Create a job with 2 nodes (and all their cores, here 4) ====
  
Line 147: Line 148:
 As expected, every job only has access to 1 single GPU. As expected, every job only has access to 1 single GPU.
  
-Regarding the logical CPUs, we see that we got those given by OAR along with their thread sibling. This is because OAR in Grid'5000 does not define the the siblings in its resources (using a thread resource, or given all siblings in the ''cpuset'' resource property), but uses the "COMPUTE_THREAD_SIBLINGS" option to compute them the execution time.+Regarding the logical CPUs, we see that we got those given by OAR along with their thread sibling. This is because OAR in Grid'5000 does not define the the siblings in its resources (using a thread resource, or given all siblings in the ''cpuset'' resource property), but uses the "COMPUTE_THREAD_SIBLINGS" option to compute them at the execution time.
wiki/coupling_oarsh_with_gnu_parallel_to_mimic_salloc_srun.txt · Last modified: 2020/04/16 15:45 by neyron
Recent changes RSS feed GNU Free Documentation License 1.3 Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki