4 ms·
> Completely true, but at that point we're running a cloud within a cloud You're doing that anyway, even if you run one job per machine, you just loose granula
by jedberg 11y ago
> Completely true, but at that point we're running a cloud within a cloud
You're doing that anyway, even if you run one job per machine, you just loose granularity (one of the big advantages of any "cloud").
> In other words, a farm of huge machines will need a queue to keep them busy. Having a queue means there's some delay before a job starts
But that's only true if you can't fill one machine. Once you're filling one machine, you're queue processing time will be the same. Presumably you still have a queue, it's just that the queue drives the start of machines instead of processes on the machine.
> That requires less engineering
Right, like I said, you can do less engineering now but pay more later as your workloads scale up in both money and maintenance costs.