This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
wiki:managing_resources_cpu_gpu [2019/11/19 17:56] – [Second scenario, more complex] neyron | wiki:managing_resources_cpu_gpu [2020/03/03 13:31] – [Managing processing unit topologies] neyron | ||
---|---|---|---|
Line 11: | Line 11: | ||
In database these 4 kinds of resource properties are all stored as **columns** of the '' | In database these 4 kinds of resource properties are all stored as **columns** of the '' | ||
- | **Given a hierarchy** (chosen by the administrator for its cluster setup, for instance cluster/ | + | **Given a hierarchy** (chosen by the administrator for his cluster setup, for instance cluster/ |
| | ||
One rule must be kept in mind: **any unique object in the resources hierarchy must have a unique id among its set of object**. For example: | One rule must be kept in mind: **any unique object in the resources hierarchy must have a unique id among its set of object**. For example: | ||
Line 168: | Line 168: | ||
When reserving 1 GPU, the user obviously gets the 3 cores associated to the GPUs. | When reserving 1 GPU, the user obviously gets the 3 cores associated to the GPUs. | ||
- | GPU job can be tied to GPU resources (where '' | + | Finally, |
<code perl> | <code perl> | ||
foreach my $mold (@{$ref_resource_list}){ | foreach my $mold (@{$ref_resource_list}){ |