3 ms·
It's up to you to see it the other way around: if you optimize jobs you can fit future workloads in the infrastructure you've already paid for. I prefer to thi
by pantulis 8y ago
It's up to you to see it the other way around: if you optimize jobs you can fit future workloads in the infrastructure you've already paid for.
I prefer to think of reserved instances as a purely financial trick.
- Ironlink 8y agoRight, but that requires your new workloads to fit well with the resources you have committed to. If you've committed to many small machines, they may not be well suited to an especially heavy workload. If you've skewed your commitment towards a large amount of memory per compute (or vice versa), you can find yourself with lots of RAM (or compute) and no natural use-case. At the bottom line, commitment impedes change.
- pantulis 8y agoYour point is valid, thanks for the answer.
- room271 8y agoThe pay-as-you-go reductions give you more flexibility about when you make optimisations to your code though and help you handle uncertainty around this. For example, if I have a new workload that won't fit on existing hardware with AWS, I can either: a) reserve the new instances, or b) not reserve on the assumption I will be able to optimise in the 'near' future. In practice this is hard to know but AWS forces you to come to a correct decision up front, whereas Google Cloud allows you to not have to answer this up front without being punished later for making the 'wrong' choice.