The resident is there to absorb *spikes* in traffic, not to handle standard traffic operations. In an *ideal* world, what should be happening is that you start out with resident instances. Traffic comes in, then the scheduler kicks up a dynamic instance while simultaneously directing some traffic to resident instances to process. Once the dynamics are up, then the requests go to the dynamic instances while residents return to idle. It doesn't always work that way, but that's the general idea.
Can you double check your logs, and specifically look at the instance id that is recorded on each log? Sometimes it can look like the dynamic instance is handling the request, when in reality the resident is handling the request; the simultaneous processes can sometimes confuse people. ----------------- -Vinny P Technology & Media Advisor Chicago, IL @GOV on AppDotNet: https://alpha.app.net/gov On Wednesday, April 3, 2013 11:07:03 PM UTC-5, aswath wrote: > > Hello, > I have the appid Application settings > Idle instances: 1 - Automatic > > My app is idle, and I can see the logs, that there is no traffic > There is one Resident instance. > > Now, I issue a servlet request from my browser > - New instance is created > - the request is served by the new instance > > What is the purpose of Resident instance? > > Google team, please suggest for the appropriate settings to avoid this > situation > > -Aswath > -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
