Your app will run well if you use auto for max idle instances, but you should not have to do that and it is expensive. When things are running like they should you can tune it based on your traffic. Ours is very smooth so we can safely set it to a fairly low setting and it runs well. We leave some room for an odd process to spike our average latency (and thus spin up instances). That could be your issue though. Depending on how much traffic and how much it varies, 6 idle instances might not be enough to handle the ramp up and it's choking out your users. (not enough instances for the traffic spikes)
What I meant by churn is lots of instances dying (from memory limits, errors or unknown infrastructure issues) or shutting down due to your max idle instances being too low for your ramp up/down rates and then getting started again. On Wednesday, April 11, 2012 11:07:55 AM UTC-5, Jeff Schnitzer wrote: > > On Wed, Apr 11, 2012 at 11:30 AM, Nicanor Babula > <[email protected]> wrote: > > Hi Mike, > > > > Thanks for your answer. > > 1) The ages of the instances span from 8 minutes to 30 minutes. What do > you > > mean by instance churn? > > 2) > > Idle instances: 1 - 6 > > Pending latency: Automatic - Automatic > > I presume you mean you have Min Idle Instances set to 1 and Max Idle > Instances set to 6. > > Set these to Auto-Auto. It's been a couple months since I last > touched these settings, but every time I did I got a crappy UX with > lots of user-facing loading requests. Since going to Auto-Auto our > app has been consistently snappy. > > Jeff > > -- 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/-/p3BNM_Fs4bUJ. 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.
