On mySimon: Nike SB Eugene Backpack
BNET Business Network:
BNET
TechRepublic
ZDNet
TalkBack 1 of 7:
Next »
CPU pricing comparison is misleading
EC2 charges by the instance-hour. That is, it costs 10c per hour that each of your EC2 instances is up ($72/month for one instance), regardless of how much load is being put on each instance.

If Google is charging by the "CPU core-hour", implying that it's a pay-as-you-go model. You pay for the cycles that your app burns; if your app is hammered, you'll be paying for multiple CPU core-hours per elapsed real-time hour (as if you'd spun up multiple EC2 instances to handle the extra load). While you're idle, though, you wouldn't pay anything.

I'd say that the Google scheme is a lot fairer, though that's only possible because your app logic only runs on demand, in a fixed environment (rather than your own Unix image).
Posted by: Jason Etheridge   Posted on: 05/29/08 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

CPU pricing comparison is misleading  Jason Etheridge | 05/29/08
also means people will be motivated to write efficient code  stevey_d | 05/30/08
RE: Google App Engine pricing a disappointment  D. T. Schmitz | 05/30/08
Amazingly uninformed opinion  Filip Verhaeghe | 05/30/08
RE: Google App Engine pricing a disappointment  BIGELLOW | 05/30/08
RE: Google App Engine pricing a disappointment  jperkins@... | 05/30/08
Thank You Google for a $70 per month subsidy  albeit | 05/31/08

What do you think?

SponsoredWhite Papers, Webcasts, and Downloads

advertisement
advertisement

SmartPlanet

Click Here