Differences

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

--- wiki:coupling_oarsh_with_gnu_parallel_to_mimic_salloc_srun [2020/03/03 13:28] – [PoC with cores] neyron
+++ wiki:coupling_oarsh_with_gnu_parallel_to_mimic_salloc_srun [2020/04/16 15:45] (current) – [PoC with cores] neyron
@@ Line 1: / Line 1: @@
-Proof of concept of using ''GNU parallel'' with ''oarsh'', so that a user can execute batch (''parallel'') jobs using subsets of the resources allocated to a bigger (''OAR'') job.
+Demonstration of the use of ''GNU parallel'' with ''oarsh'', so that a user can execute batch (''parallel'') jobs using subsets of the resources allocated to a bigger (''OAR'') job.
 E.g. 1 batch per core (or gpu), in a job which has many nodes/cores/gpus allocated.
-This requires the changes made in this [[https://github.com/oar-team/oar/tree/2.5_oarsh_on_a_sub_set_of_resources_a_la_srun|branch]], especially this
+This requires OAR 2.5.9 which is only available in beta version for now (oar-2.5.9+g5k6)
-[[https://github.com/oar-team/oar/commit/72a6cce952a3fa736872d69c6e72fb2d8ffac5de|commit]]
-(not merged yet).
 ===== PoC with cores =====
@@ Line 148: / Line 146: @@
 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 a 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.