aswath, Barry is absolutely correct when he says that, "Unless you can provide real verifiable evidence, there is probably little Google can do. They need something to investigate."
However, don't waste your time on this issue. Collecting "real verifiable evidence" on the ever-changing scheduler behavior has proven (time and time again) to lead to no investigation by Google. I repeat, don't waste your time on this issue. My advice is to focus on the things that make you happy. A week or two from now, without warning, this scheduler behavior will change. Weeks later it will change again, and on it goes. David On Thursday, April 4, 2013 8:54:30 PM UTC-6, aswath wrote: > > The view logs link in the instances screen does not show logs or is > broken. Hence, you cannot find out which instance served the traffic. > > -Aswath > > On Thu, Apr 4, 2013 at 10:59 PM, Vinny P <vinn...@gmail.com > <javascript:>>wrote: > >> 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 tell where is this documented? Whey should the resident instance > be idle, and the traffic served by dynamic instance, with resident instance > being idle. > What is the use of the pending latency setting in the Application Settings. > I have set it to 4sec - automatic. With this setting, I understand that, > if there is a request waiting in the queue for less than 4s, then it should > be served by the resident instance. There is no need to create a new > instance, and getting charged for the new instance hours. > > >> 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.
