Skip to content

Definition of resources #6

Description

@davidwaroquiers

How to have a definition of (requested or assigned) resources that are easy to understand, but still keeps a sufficiently sophisticated level of granularity as well as the possibility of heterogeneous resources (both in type, e.g. CPUs+GPUs and numbers, e.g. one node with 4 cores and X Mb of memory and 3 nodes with 8 cores and Y Mb of memory).

At the (simplest) level of cpus/processors/cores, a naming convention should be adopted (there does not seem to be any standard that stands out on this). One example could be:
Smallest computing "entity": CORE
A PROCESSOR is made of several COREs
A NODE is made of several PROCESSORs
A Supercomputer has many NODEs (possibly different in types/sizes/...)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions