Replies: 1 comment
-
@tom95858 @morrone I created a discussion page you can add results and etc to for the comp_id issue. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In metric sets, component_id is 64 bits for arbitrary definition by system administrators to make some aspect of data analysis easier downstream. The per-metric udata field has also been used on some systems to carry per-metric data origin information. The use of component_id with LDMS on TOSS3 systems has been as a convenient unique numeric alias for hosts within a computing center.
Other, hierarchically decomposed bit assignments have been prototyped in the past.
As a result of the 5/27/2021 ldms users meeting on component_id, Tom T. has proposed to prototype something like the following:
Ben A. further suggests bit decomposition of host_id, if it is limited to 32 bits) as follows:
high 1:reserved
next 3: network-id-number (max: 8 networks)
next 7: cluster-id-number (max: 128 clusters/network)
next 4: node-type-id-number (max 16 node types)
next 17: node-id-number (max 128k nodes/type/cluster)
Beta Was this translation helpful? Give feedback.
All reactions