Hi Greg, Thanks for this update. If find it very satisfying. The only thing I don't fully approve is the 15 minutes start-up fee, I would prefer more transparency and control, with scheduler knobs "Max idle time" and "Min idle time". But then I guess scheduler tuning could become very complicated and unpredictable... However, I don't feel comfortable knowing that my bill will depend on a scheduler I don't control much, nor understand clearly.
Anyway, when looking at the new pricing model for the Datastore API, I saw an opportunity to help developers optimize their code for lower bills. As a Java Developer, I do a lot of local unit testing involving the Datastore. Could it be possible to provide as a test output the number of each Datastore operation, and the calculated cost of the executed code ? It would allow us to test different approaches in using the Datastore API and finding which are the most cost-effective without having to do the math ourselves. I even had the funky idea that this could be used in production, in an application that bills its users with a "pay for what you use" model. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/1U7kodMw5vAJ. 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.
