Kubernetes Borg/Omega history topic 9: Scheduling constraints. I have volumes more to write about configuration, but will move on with history topics for now. Borg's set of constraints grew organically over time. It started with just required memory, before multicore and NPTL
-
Show this thread
-
Replying to @bgrant0607
One notable borg resource "failure" I recall was a naive network interface bandwidth resource ("Job requires 10Mbps"). Turns out networking is pair-wise and difficult, and this was better handled as relative priorities (and aggregate constraints) - good to remember for k8s.
1 reply 0 retweets 0 likes
Replying to @anguslees1
Network is hard, due to burstiness, compressibility, nonlocal capacity limits (switches), network QoS, behaviors in the network stack, etc. Disk I/O is also hard
12:21 AM - 10 May 2019
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.