4 ms·
> if you have a specialised workload (CPU heavy, storage heavy, etc) there's definitely cost savings at scale for DIY I wasn't sure what your use "heavy" means
by tedchs 9y ago
> if you have a specialised workload (CPU heavy, storage heavy, etc) there's definitely cost savings at scale for DIY
I wasn't sure what your use "heavy" means here -- is it "a lot of" or "disproportionate"? Years ago there was much less flexibility with IaaS machine shapes, but I was super impressed when Google launched "custom machine types". There's a little slider to scale up/down your RAM/CPU independently, and of course storage is already independent. In fairness, there is some correlation between CPU allocation and storage IOPS, but that's inherent to scheduling a portion of the host machine reasonably.
https://cloud.google.com/compute/docs/instances/creating-instance-with-custom-machine-type https://cloud.google.com/compute/docs/instances/creating-ins...
- guitarbill 9y agoYeah, if you're using loads of CPU, but not all the RAM or block storage. This usually happens if your problem isn't really parallelisable. Then scaling out isn't really something you can do easily or quickly, so the cloud loses it's appeal a bit. In those cases, it might make sense to go DIY/in-house.