3 ms·
It's easy, though? On Docker, --cpuset-cpus=0 will pin the container to the first core. K8s: https://kubernetes.io/docs/tasks/administer-cluster/cpu-managemen
by 3np 2y ago
It's easy, though?
On Docker, --cpuset-cpus=0 will pin the container to the first core.
K8s: https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/ https://kubernetes.io/docs/tasks/administer-cluster/cpu-mana...
CPU affinity and pinning is something I think you should be able to achieve without too much hassle.
- edude03 2y agoI think the point was this isn’t the norm though. If you know you need to be pinned to a core you CAN configure kubernetes to do so but it’s not the default and therefore you are unknowingly leaving performance on the floor
- 3np 2y agoI'm quite certain you'd leave more performance on the table by pinning in general and on average. Just let the CPU scheduler do its job. Unless you know better, in which case, by all means go ahead and allocate computational resources manually. I don't see a way to make that a sensible default, though.
- seabrookmx 2y ago> It's easy though Neat, I didn't know it was a single flag in Docker. The k8s method you linked definitely has some caveats as it doesn't allow this scheduling at the pod level, and requires quite a bit of fiddling to get working (atleast on GKE). This isn't even available if you use a fully managed setup like autopilot. Maybe my expectations just aren't realistic but "easy" to me would mean I put the affinity right next to my CPU request in the podSpec :/