On Sun, Aug 26, 2012 at 11:25 PM, Mobicage <c...@mobicage.com> wrote: > Hi > > Can somebody explain how it is possible that > - I have 1 "resident" java appengine instance > - I didnt send any test requests for 90 minutes > - When I sent the request, the system had to warm up, although I have 1 > resident java appengine. > > What does resident exactly mean?
I believe Jon described resident in great details in this thread: https://groups.google.com/d/msg/google-appengine/nRtzGtG9790/hLS16qux_04J """ Because the scheduler is now treating the reserved instances as Min-Idle-Instances, what you're describing is expected behavior. They are intentionally kept idle, and it tries to serve traffic using the non-reserved instances. Then, if the non-reserved instances can't keep up, then it will make use of the reserved instances. That is, to repeat, the invariant that the scheduler is trying to maintain here is that your app has at least 3 idle instances. And if an instance is getting traffic, then it isn't idle. The value of an idle instance is that it can process requests right-away if needed, without having to first warmup or do a loading request. It sounds like what you'd really prefer is something like Min-Instances, but that's not presently an available option. """ The scheduler route traffic to resident idle instance when dynamic instances can't keep with the traffic and always try to keep Min Idle Instances in reserve at all times, I believe it currently need to start at least 1 dynamic instance before making use of the resident idle capacity. > My settings are: > * Idle Instances: ( 1 – 1 ) > * Pending latency: (Automatic - 500ms) > > Logs (blanked out some stuff with xxx): > > 2012-08-24 22:14:43.786 /xxx 200 8872ms 0kb AppEngine-Google; > (+http://code.google.com/appengine; appid: s~xxx) > 0.1.0.40 - - [24/Aug/2012:15:14:43 -0700] "POST /xxx HTTP/1.1" 200 793 - > "AppEngine-Google; (+http://code.google.com/appengine; appid: s~xxx)" > "xxx.appspot.com" ms=8873 cpu_ms=5157 cpm_usd=0.000089 loading_request=1 > instance=00c61b117c1360f2e8f3cdce153a3c79777a7e81 > > I 2012-08-24 22:14:43.786 > This request caused a new process to be started for your application, and > thus caused your application code to be loaded for the first time. This > request may thus take longer and use more CPU than a typical request for > your application. > > 2012-08-24 20:46:47.635 /xxx 200 1862ms 0kb AppEngine-Google; > (+http://code.google.com/appengine) > 0.1.0.2 - - [24/Aug/2012:13:46:47 -0700] "POST /xxx HTTP/1.1" 200 0 "xxx" > "AppEngine-Google; (+http://code.google.com/appengine)" "xxx.appspot.com" > ms=1863 cpu_ms=260 cpm_usd=0.000260 queue_name=default > task_name=9251619801338774487 > instance=00c61b117c266e667e6954feaef8bf2492f23006 > > Thank you! > > > On Wednesday, August 22, 2012 9:58:44 PM UTC+2, Mos wrote: >> >> Does anybody else experience abnormal behavior of the instance-scheduler >> the last three weeks (the last 7 days it got even worse)? (Java / HRD) >> Or does anybody has profound knowledge about it? >> >> Background: My application is unchanged for weeks, configuration not >> changed and application's traffic is constant. >> Traffic: One request per minute from Pingdom and around 200 additional >> pageviews the day (== around 1500 pageviews the day). The peek is not more >> then 3-4 request per minute. >> >> It's very obvious that one instance should be enough for my application. >> And that was almost the case the last months! >> >> But now GAE creates most of the time 3 instances, whereby on has a long >> life-time for days and the other ones are restarted around >> 10 to 30 times the day. >> Because load request takes between 30s to 40s and requests are waiting >> for loading instances, there are many request that >> fail (Users and Pingdom agree: A request that takes more then a couple of >> seconds is a failed request!) >> >> Please check the attached screenshots that show the behavior! >> >> Note: >> - Killing instances manually did not help >> - Idle Instances were ( Automatic – 2 ) . Changing it to whatever didn't >> not change anything; e.g. like ( Automatic – 4 ) >> >> Thanks and Cheers >> Mos >> >> >> >> >> >> > -- > 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/-/YT9dk2OEsg8J. > > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. -- Johan Euphrosine (proppy) Developer Programs Engineer Google Developer Relations -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
