You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* add cpuset_test.go
* fix very large inputs causing crash
* fix copyright on cpuset_test to match the DD copyright entries
* add back in the default header so circle does not fail the header check
* is this correct?
* think this worked
* update cpuset.go
* switch to get gocritic to be happy
* add cpu limit to doc
Copy file name to clipboardExpand all lines: docs/cpu_pressure.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ When the injector pod starts:
38
38
39
39
> NB: stressing 100% of the allocated cpuset DOES NOT MEAN stressing 100% of all cores allocated if the defined CPU is below 1 in Kubernetes (e.g. `100m`)
40
40
> NB2: container being part of the same pods can have similar core associated, however we still need to stress each of them like if they were alone, linux CPU scheduler is the one that will throttling us appropriately
0 commit comments