4 ms·
Google screwed up by trying to charge for CPU time in the first place. CPU time is an overabundant resource in the cluster, RAM is precious. This change was i
by stickfigure 15y ago
Google screwed up by trying to charge for CPU time in the first place. CPU time is an overabundant resource in the cluster, RAM is precious. This change was inevitable.
Look at Linode, Rackspacecloud, even EC2. They all charge primarily by the megabyte. I don't like it either, but it's the unfortunate economic reality.
- groks 15y agoGoogle doesn't seem to think that RAM is the limiting resource: "Most frontend instances don't come near their RAM limit, and most of their RAM consumption is on shared data like packages." -- nickjohnson http://goo.gl/SOeSF http://goo.gl/SOeSF
- stickfigure 15y agoActually, if you look at the context, this reinforces my point that RAM is the limiting factor. Nick mentioned this to reassure some other user worried about Google lowering the RAM limit. As long as Google is being conservative WRT oversubscribing RAM, the instance RAM limit is the true measure of the cost of an instance. It's not about how much you use, it's about how much you could use.