Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
usage of AVX instructions by a container can affect other on the same host #67355
Is this a BUG REPORT or FEATURE REQUEST?:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
This has been discussed a lot in Resource Management WG. There was a proposal (actually two proposals) to implement CPU pooling to fix this. See documents
The documents have been shared to at least
The thinking in the WG is that the easiest solution is to use taints and tolerations for separating AVX and non-AVX workloads on separate nodes. If a CPU pooling scheme is adopted, it should rather be automated (or based on SLOs) than user-configured.
This issue exists in any application environment that uses Intel's recent CPUs. What is the general solution offered by Intel for shared environments? Would it be possible to dynamically disable AVX instruction on nodes where it is not needed?