On Wed, Mar 14, 2012 at 4:28 AM, Tapir <tapir....@gmail.com> wrote: > > On Mar 14, 1:17 pm, Gopal Patel <patelgo...@gmail.com> wrote: >> you mean, always have one instance more than required ? ( who is going to >> pay for that ? ) , and is not minimum idle instance same thing ? > > It is different with the normal resident instance. > It is an instance to handle requests only at the time of the situation > "no available instances and need create a new instance", > so that many "Cold Starts" can be avoided.
This is pretty much exactly what setting minimum idle instances does. Requests are preferentially routed to dynamic instances rather than resident instances. The problem is, something in the scheduler is broken. Instead of routing requests to the idle instance, GAE prefers to route requests to a fresh instance, causing the user to wait while an instance warms up. That setting is probably best described as "minimum useless instances". Maybe somebody took the "minimum _idle_ instances" label too literally ;-) This is the behavior I observed a week or two ago. Hopefully it will be fixed. Doesn't sound like it has been so far. Jeff -- 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.
