Differences

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

--- wiki:managing_resources_cpu_gpu [2019/11/19 17:57] – [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 ''resources'' table. A rows then gives the set of properties for one resource.
-**Given a hierarchy** (chosen by the administrator for its cluster setup, for instance cluster/switch/host/cpu/core, but thread could be added, or other customizations), one row in the table gives information for the **lowest level of resources of the hierarchy** (e.g. core). Then **groups of lines** define higher levels, like Russian dolls (e.g. ''#C'' rows for CPUs, ''#H*#C'' rows for hosts, ...).
+**Given a hierarchy** (chosen by the administrator for his cluster setup, for instance cluster/switch/host/cpu/core, but thread could be added, or other customizations), one row in the table gives information for the **lowest level of resources of the hierarchy** (e.g. core). Then **groups of lines** define higher levels, like Russian dolls (e.g. ''#C'' rows for CPUs, ''#H*#C'' rows for hosts, ...).
 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: