Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add paragraph on resource types in the resource application #370

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

itkovian
Copy link
Collaborator

No description provided.

@itkovian itkovian force-pushed the tier1-credits-explanation branch from 6a7354d to 5009ac2 Compare November 13, 2023 12:45
Resource types:

* credits: These are the consumable units in CPU-hour equivalents for CPU, memory, and GPU allocation in the job. This means that requesting e.g., all the memory of a node
will cost you the equivalent of using all the cores on this node. Similarly for each GPU hours consumed, 12 credits are allocated. These are also the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GPU hours -> GPU hour

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i would use another word then cost


* credits: These are the consumable units in CPU-hour equivalents for CPU, memory, and GPU allocation in the job. This means that requesting e.g., all the memory of a node
will cost you the equivalent of using all the cores on this node. Similarly for each GPU hours consumed, 12 credits are allocated. These are also the
limiting factor w.r.t. total awarded compute time on the system for your project (limited hard by the resource scheduler). The cost is computed as the maximum of all three
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the cost is not computed like that. it's credits * price percredit + gpuhours * price per gpuhour, where price per credit is mentioned as prive per cpu hour in the contract

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so the contracts should only be corrected to specify CPU hour equivalent instead of CPU hour (and we can avoid mentioning the word credit.
and maybe CPU hour equivalent can also be used in the resapp instead of credit?

* credits: These are the consumable units in CPU-hour equivalents for CPU, memory, and GPU allocation in the job. This means that requesting e.g., all the memory of a node
will cost you the equivalent of using all the cores on this node. Similarly for each GPU hours consumed, 12 credits are allocated. These are also the
limiting factor w.r.t. total awarded compute time on the system for your project (limited hard by the resource scheduler). The cost is computed as the maximum of all three
resource-equivalents.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i would first describe what the resources are and what a resource-equivalent is. or not use new words ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants