On 7 August 2013 11:57, Cristi eXPV <[email protected]> wrote: > There should really be a option to limit to a specific number of > instances, no matter what. > In the application settings menu all you can do is to limit the maximum > number of IDLE instances, which I'm not sure if it works as intended. I > mean I set the *Max Idle Instances* to 1
That actually means AppEngine aims to keep an idle instance around, just that it shouldnt aim for more than 1. So even if you actively serving requests with one instance, another idle one will be kept alive. The 'idle' instance is there to handle the first request that the active intance(s) can't handle - while a new instance is being spun up. The new active instance will continue serving requests and the buffer instance will go back to being idle again. You should keep it on Automatic, to help avoid this (as best as I can gather). > and the *Min Pending Latency* to 15 seconds, but I still see 2 instances > running occasionally, for long period of times with no requests. Aren't > they supposed to close after 15 min of being idle? They can be closed - if AppEngine needs the capacity for other requests. But if the capacity isnt needed you get to keep the instance for free. ie you shouldnt be charged for it (well wont come out of the free quota). > And why does it even fire a seconds instance with those settings, > considering that no request reached 15 seconds delay? > See above. > > I run a simple "what's my IP" python app, that really doesn't need high > performance. I mean it really doesn't make a difference if the response is > after 100ms or 5 seconds, all it matters is that only one instance is > running, so that those daily 28 instance hours don't ever run out. Unfortunately you generally at odds with how AppEngine is designed, and targeted. Its really meant for apps that do want scale, and quickly ramp up the requests. The rather genorous free quota does allow you to run toy apps for very little down, but its not really the market. In general it sounds like using modules to deploy your app on a "Basic Scaling" module would be ideal. That way can avoid the "Automatic Scaling" you get with normal frontend instances. Alas it still seems to be tied to frontend/backend instance quotas, so a Basic Scaling module will use your 9 hour quota, not the 28 hour front end quota. Maybe as modules mature, could use the free quota to run a single basic scaling instance rather than automatic scaling ones. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
