I think there's a better way to think about economies of scale (looking at it through the lens of Google Cloud). Let's quantify your workload as "resource-seco

I think there's a better way to think about economies of scale (looking at it through the lens of Google Cloud). Let's quantify your workload as "resource-seconds", what many of Google's services (and some AWS services, like Lambda) allow you to do is maximize resources and minimize seconds (assuming efficient parallelization of workload, which is afforded by Google's super-awesome Networking). Cost is the same to you, but you get your results faster. This is afforded by the scale and by the multi-tenant nature of underlying services. This model can only work when there's lots of folks using such a service. (work on Google Cloud Big Data)