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

docs: remove cores/memory beta label, update driver cpu docs #16175

Merged
merged 2 commits into from
Feb 14, 2023

Conversation

shoenig
Copy link
Member

@shoenig shoenig commented Feb 14, 2023

Closes #13775

@@ -1138,6 +1138,11 @@ many CPU shares are available to your process by reading `NOMAD_CPU_LIMIT`.
Please keep the implications of CPU shares in mind when you load test workloads
on Nomad.

If resources [cores][cores] is set, the task is given an isolated reserved set of
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
If resources [cores][cores] is set, the task is given an isolated reserved set of
If resources [`cores`][cores] is set, the task is given an isolated reserved set of

If resources [cores][cores] is set, the task is given an isolated reserved set of
CPU cores to make use of. The total set of cores the task may run on is the private
set combined with the variable set of unreserved cores. The private set of CPU cores
is available to your process by reading `NOMAD_CPU_CORES`.
Copy link
Contributor

Choose a reason for hiding this comment

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

for the task. This may not be used with `cpu`.
- `cores` <code>(`int`: &lt;optional&gt;)</code> - Specifies the number of CPU cores
to reserve specifically for the task. This may not be used with `cpu`. The behavior
of setting `cores` is specific to each task driver (e.g. [docker][docker_cpu], [exec][exec_cpu]).
Copy link
Contributor

Choose a reason for hiding this comment

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

I wonder if it would make sense to expand task driver capabilities to include core reservation. That way we would be able to validate if the a task uses cores with a task driver that doesn't support it.

Copy link
Member Author

Choose a reason for hiding this comment

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

Interesting idea - added to https://github.com/hashicorp/team-nomad/issues/373 along with thinking of PSI uses

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.

Remove beta label from cores/memory_max fields
2 participants