>> The smallest granularity will be 15 minutes, but part of the scheduler change is to ensure we don't start instances to serve 1 request.
This is useful to know so thank you for letting us know this. But it's disappointing to say the least. We're going from millisecond granularity with CPU-hours to chunks up to 15 minutes depending on how many requests you get out of a new instance. Anyway, in the FAQ, I'd like a transparent, honest answer about why the switch from CPU-hours to instance-hours (not a vague 'based on the value of the service', 'based on feedback'), and a comprehensive outline of the ramifications. Thanks, -Peter -- 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.
