+1 on usage-based billing. It was a HUGE factor in our decision to use App Engine; we have built all of our company's products on App Engine.
On a related note, the 15-minute cost to spin up new instances defeats one of the greatest features of App Engine: the ability to fan-out and process large jobs very quickly. We have architected many processes that take advantage of this feature: various stats compilations, Map- Reduce data migrations, large scale batch import and report generation. It was always an amazing power of App Engine to scale-out and chew through these jobs in very little time. Now, to scale out, we will incur a bunch of extra billing in order to warm up the instances. Our solution, I guess, will be to tune back our queue rates and force the jobs to run longer. Seems like a waste of a great infrastructure. j -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
