I'm not sure I understand this. I have a very low traffic app and I've set the min idle instances to automatic and the max idle instances to 1. Once I did this I have never been charged for more than one instance even during high latency periods. Before I set this limit to one I had it set to 5 and during those high latency periods I would get the surprise bill from hell for almost no actual traffic. Google says "You will not be charged for idle instances over the specified maximum." Which to me indicates that yes you can limit the number of instances (at least for billing purposes.) I guess the problem with this is that you get crap latency if your actual traffic does spike regardless of GAE latency issues.
Maybe it would be nice if AE latency degrades X% then you get X% more free instances during that period or something. On Wednesday, June 13, 2012 1:51:25 PM UTC-7, Simon Knott wrote: > > ... > At the moment you have no way to limit the instances - if the scheduler > went completely awry, they could keep spinning up instances until the cows > come home and you have no way to stop it. > ... > > -- 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/-/J3Hzv1U-3fUJ. 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.
