3 ms·
I'd rather have Google say "in order for GAE to stay alive, we've had to raise pricing on our current metrics to X", I can understand that, I can justify that,
by bane 15y ago
I'd rather have Google say "in order for GAE to stay alive, we've had to raise pricing on our current metrics to X", I can understand that, I can justify that, I can compare it and decide how to deal with it/optimize for it, but instead we got, "based on user popular feedback we're radically changing the way we measure usage, then charging some significant multiplier to whatever everybody is already paying so that it no longer makes sense to operate on our platform and you can't even really compare it in such a way as to make sense of the change, then we'll systematically not address anybody who asks us about this in forums or via other communications but we're going to do all this in the most frustratingly passive aggressive way possible" [1][2] Can anybody really believe that popular feedback to Google was "we're not being gouged nearly enough, Google, charge us 2000% more!"
[1]http://googlecode.blogspot.com/2011/05/google-app-engine-new-version-and.html http://googlecode.blogspot.com/2011/05/google-app-engine-new...
"Over the last three years, we’ve collected great feedback from our customers and now believe that the biggest thing we can do to help our customers is to graduate App Engine from preview status. "
"Adding business features will help App Engine meet a broader set of needs and the new, more transparent pricing model will help customers better align their App Engine investment with their business goals."
[2]http://googleappengine.blogspot.com/2011/05/year-ahead-for-google-app-engine.html http://googleappengine.blogspot.com/2011/05/year-ahead-for-g...
"App Engine graduating from Preview later this year!
Based on this feedback we’ve decided to make some fairly large changes:"
"In order to become an official Google product we must restructure our pricing model to obtain sustainable revenue. Based on customer feedback this means focusing on usage-based pricing and placing per-user, per-app pricing on hold until further notice."
- stickfigure 15y agoGoogle 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.