4 ms·
Are you setting cpu requests in your pod spec? This influences the cgroup cpu.shares for the containers and (unless this has been fixed) leaving cpu requests un
by uberduper 4y ago
Are you setting cpu requests in your pod spec? This influences the cgroup cpu.shares for the containers and (unless this has been fixed) leaving cpu requests unset results in cpu.shares=2, which jvm interprets badly.
- pritambarhate 4y agoThanks for replying. Yes we are setting the CPU requests in our pod spec. I will experiment with this further and see if solves the issue.