Re:Google App Engine Pricing Angers Developers, Kills PlusFeed
by mtogo on Friday September 02, 2011 @08:46PM
(#2956133)
The problem is the price, though. Spinning up a couple EC2 micro instances to run your app is $0.02/hr per instance and you can run a few threads per instance. Appengine is $0.04/hr (double that soon), with one thread per instance.
Re:Google App Engine Pricing Angers Developers, Kills PlusFeed
by jcheng on Friday September 02, 2011 @01:37PM
(#2954905)
Thanks for the info. Is there a setting for max number of simultaneous instances? If your app gets slashdotted are your potential costs completely unbounded?
(Just out of curiosity, I'm not a GAE customer)
Re:Google App Engine Pricing Angers Developers, Kills PlusFeed
by angkec on Friday September 02, 2011 @04:21PM
(#2955452)
No there isn't. Just "max idle instances". So you'll get a huge bill if you get slashdotted.
Re:Google App Engine Pricing Angers Developers, Kills PlusFeed
by groks on Sunday September 04, 2011 @06:19AM
(#2959179)
You won't, because you specify a maximum daily spend in the budget settings. So when you get slashdotted the scheduler will spin up X hundred instances, your budget will run out in 1/2 hour, and your site will be down for anything up to the next 23 1/2 hours.
> The Idle Instances slider allows you to control the number of idle instances available to your application at any given time. Idle Instances are pre-loaded with your application code, so when a new Instance is needed, it can serve traffic immediately. You will not be charged for instances over the specified maximum. A smaller number of idle Instances means your application costs less to run, but may encounter more startup latency during load spikes.
There is another setting for latency:
> The Pending Latency slider controls how long requests spend in the pending queue before being served by an Instance. If the minimum pending latency is high App Engine will allow requests to wait rather than start new Instances to process them. This can reduce the number of instance hours your application uses, but can result in more user-visible latency.
So if you are fine with a little higher latency for your app then you can reduce your bill by a great deal. If you want all that GAE can offer with max. instances available and lowest latency you gotta pay - as you would when you run n instances at another cloud provider.