-
Notifications
You must be signed in to change notification settings - Fork 153
Issues: uber-go/automaxprocs
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
How does it work? How does it automatically set the value of GOMAXPROCS based on the cgroup?
#84
opened Nov 23, 2023 by
JokerDevops
What happens if cpu quota on k8s side is less than 1 core?
#54
opened Apr 14, 2022 by
timo-klarshift
qurying memory quota not work when /proc/self/mountinfo match multiple keywords
#41
opened Jul 19, 2021 by
coco-roll
no cgroup mountinfo in /proc/self/mountinfo if shareProcessNamespace=true
#38
opened May 13, 2021 by
stonewesley
Provide an API to expose the read value without setting GOMAXPROCS
#29
opened Jul 15, 2020 by
ajwerner
ProTip!
Exclude everything labeled
bug
with -label:bug.