13 ms·
So they built...a scheduler?
by naturalgradient 9y ago
So they built...a scheduler?
- mnx 9y agoWell, a multi-machine scheduler.
- robnagler 9y agoIn the HPC world, there are many of these: SLURM, Torque, PBS.
- toomuchtodo 9y agoDon't forget Globus and Condor!
- pnutjam 9y agoHow could you overlook (son of) Grid Engine
- samstave 9y agoWell yes, but the elegance here is how they layered their scheduler to be on top of scheduling the resources they paid for at AWS with a meta-scheduler, which when they originally did this was rather novel in the consumer market.
- brucephillips 9y agoNo, the underlying instances were reserved. It reduces to the same problem as scheduling on bare metal.
- samstave 9y agoSo, are you saying this is simplistic.? What is your solution.?
- brucephillips 9y agoIt's not simplistic. It's simple. And a fine solution.
- samstave 9y agoAh yes, good correction of the statement. I think we both agree, just that I was more clumsy with my language. Thanks
- svachalek 9y agoScheduling implies this is simply done on a clock, while this is more about real-time maximization of CPU resources with feedback based on measured load.
- hobofan 9y ago> Scheduling implies this is simply done on a clock That's a very outdated definition of scheduling in regards to cloud computing. The schedulers of Mesos, Omega, Borg, etc. all do allow for CPU-load based scheduling, and have schedulers for other scenarios.