Automatically adjust GOMAXPROCS when run in a cpu-constrained container #4485
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MichaelEischer
force-pushed
the
uber-automaxprocs
branch
from
2253de8
to
612d7c3
Compare
MichaelEischer
force-pushed
the
uber-automaxprocs
branch
from
612d7c3
to
f5d5e8f
Compare
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR change? What problem does it solve?
When running restic in a Linux container with CPU-usage limits, restic now
automatically adjusts GOMAXPROCS. This helps to reduce the memory consumption
on hosts with many CPU cores.
Was the change previously discussed in an issue or on the forum?
Fixes #4128
Checklist
[ ] I have added tests for all code changes.changelog/unreleased/that describes the changes for our users (see template).gofmton the code in all commits.