Compute Engine machine types with up to 96 vCPUs and 624GB of memory

Re:Compute Engine machine types with up to 96 vCPUs and 624G... by dx034 on Friday October 06, 2017 @08:21AM (#15416205)

> Depends heavily on the projected utilization. If you know your compute node is going to be computing for the next 3 years with at least medium utilization, then the self hosted metal is probably going to be quite a bit cheaper.

Isn't that already the case for 1 month? Bare metal doesn't mean own data centre or colocation. If you go with a hosting provider most offer dedicated hardware on a monthly contract. As long as you need them longer than 1-2 months that should be significantly cheaper than Google/AWS.

[ Parent | on HN ]

Re:Compute Engine machine types with up to 96 vCPUs and 624G... by vidarh on Friday October 06, 2017 @08:45AM (#15416344)

That's usually the case for almost everything on AWS/Google. If you're using them for specific features, or for very bursty work (e.g. if you use the instances less than about 6-8 hours a day), they can be cost effective, but the moment you use instances full time and don't leverage/depend on a ton of extra services, you're paying way above the odds.

[ Parent | on HN ]

Re:Compute Engine machine types with up to 96 vCPUs and 624G... by brianwawok on Friday October 06, 2017 @09:40AM (#15416681)

Kubernetes helps this a bit with bin packing. Much easier to keep 3 32 core servers loaded than 32 4 core servers.

[ Parent | on HN ]

Re:Compute Engine machine types with up to 96 vCPUs and 624G... by vidarh on Tuesday October 10, 2017 @08:49AM (#15441308)

But that's the case whether you're using AWS or self-hosted, so it doesn't really alter that calculation much

[ Parent | on HN ]