> What I've found is that unless you've got very spiky traffic, that suddenly and > massively spikes, you can turn the max idle instances down. They more-or- > less just act like a buffer, but don't actively serve traffic. If you want better > performance turn the min-idle instances up a little, but again this doesn't > need to be too high. I generally run apps with between "automatic" and 15 > idle instances.
I find that you should very, very rarely need anywhere near that. I did a post a while back with some rough formulas, but if your Max idle time is 30 seconds minus (6x your average request time + warmup time), you can generally weather any spike. Typically if you set max pending to 1s your users will be a lot happier, and you don't have to do as much with tuning. I used to spend more time tuning max idle instances, now, I set that to 1 or 2 (depending on my instance size) and tune the max idle time. (lower means better scale) -- 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.
