After speaking with Engs, I think I can explain what is going on: Here are the current scheduling rules: (> reads as has priority for handling the incoming request)
1/ Idle Always On instance > Spawning a new Dynamic instance 2/ Spawning a new Dynamic instance > Busy Always On instance 3/ Idle Dynamic instance > Busy Always On instance 4/ Idle Dynamic instance > Idle Always On instance I will give you an example to illustrate the behavior you all noticed, that is Dynamic instance handling request while Always On is idle. (Always On instance started) - Incoming request - Always On instance handle the request - another Incoming request (Always On instance busy) - A new Dynamic instance is spawned (Dynamic instance idle, Always on instance busy) - Dynamic instance handle the request - another Incoming request (Dynamic instance idle, Always on instance idle) - Dynamic instance handle the request - No request for more than idle-dynamic-instance-timeout - Dynamic instance shut down - another Incoming request (Always On instance idle) - Always On instance handle the request Hope it makes thing clearer. As part of the new billing model you will have a scheduler knob called 'max-idle-instances' that you can use if extra idling dynamic instances are undesired. The good news is that we are open to suggestion, if you think this behavior is the wrong default, feel free to comment on that thread and I will follow up your suggestion to the Engineering team. On Wed, Jul 20, 2011 at 12:18 AM, Galoch <[email protected]> wrote: > Same here. Seems like GAE is totally ignoring Always On instances. > I also noticed that even with no user hitting our app and a single > cron job that runs every 5 minutes it is still spinning instances > every 3 minutes and then killing them in 2 minutes. > > This has been happening since after the upgrade on 14th July. During > peak load this really gets nasty and brings down the performance. > > This is the feedback I got yesterday from one of our customers since > it takes time to spin an instance (and yes we use Spring): > > "1) I found the GUI to be very laggy" > > Can someone from Google please respond? > > -- > 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. > > -- 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 [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.
