When I looked into this recently, I discovered that GAE was actually sending the new request to the guaranteed idle instance, but then also spinning up another instance at the same time, making it seem as if the request were being handled by the cold instance. The 2nd instance spinning up is working as intended; GAE is guaranteeing an idle instance, and the current warm instance is handling a request.
On Wednesday, October 17, 2012 1:35:31 PM UTC-7, Jason Collins wrote: > > The most pathological case is when you ask for 1 Min Idle Instance (so > that you get warmup requests), but if that instance is actually idle, the > scheduler sends the request to a new cold instance instead of allowing the > warm one that's sitting there to handle it. > > > -- 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/-/q1ILeclrUaYJ. 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.
