summaryrefslogtreecommitdiffhomepage
path: root/test/packetimpact/netdevs/BUILD
diff options
context:
space:
mode:
authorBen Buzbee <bbuzbee@cloudflare.com>2020-09-17 00:52:01 +0000
committerBen Buzbee <bbuzbee@cloudflare.com>2020-09-30 20:32:33 +0000
commit12731f4271ea1c42d7501b9e626044cf9aa369ca (patch)
tree2e01af8f6506f9cc949aef10a5cc4c694769841a /test/packetimpact/netdevs/BUILD
parentae59e529791e4763aaa25eee818605f17699fc67 (diff)
Use consistent thread configuration for sandbox go runtime
With cgroups configured NumCPU is correct, however GOMAXPROCS is still derived from total host core count and ignores cgroup restrictions. This can lead to different and undesired behavior across different hosts. For example, the total number of threads in the guest process will be larger on machines with more cores. This change configures the go runtime for the sandbox to only use the number of threads consistent with its restrictions.
Diffstat (limited to 'test/packetimpact/netdevs/BUILD')
0 files changed, 0 insertions, 0 deletions