> The way it is supposed to work with min idle instances set is: > - idle instance is warm and ready (let's call it I1) > - request comes in > - request goes to the idle instance at which point another instance is > immediately spun up (let's call it I2) > - you now have 1 idle instance (I2) as well as 1 instance serving traffic > (I1)
My experiences have been similar to Tapir over the last month or so. I have an app that I have been testing to try to duplicate the always on behavior in the new setup. This app has not been updated, etc., in that time, billing is enabled, no datastore access, or any other services, just dynamically generated html. First, I tried the automatic setting for idle instances, and did not keep track, but visiting the app about once a day I noticed that many of those requests were loading requests, taking 20-35 seconds to load, with subsequent requests performing fine. Next, I tried setting idle instances to 1, and visiting about once a day, 7 out of 10 initial requests to the app were loading requests, with subsequent requests performing fine. Finally, I tried setting idle instances to 2, and visiting about once a day, only 3 out of 9 initial requests were loading requests. So, better with 2, but still not what I would consider acceptable. If this is the expected behavior, I would suggest that it probably shouldn't be. - Mark On Thu, Mar 15, 2012 at 3:54 AM, Gregory D'alesandre <[email protected]> wrote: > Hey Jeff, > > The way it is supposed to work with min idle instances set is: > - idle instance is warm and ready (let's call it I1) > - request comes in > - request goes to the idle instance at which point another instance is > immediately spun up (let's call it I2) > - you now have 1 idle instance (I2) as well as 1 instance serving traffic > (I1) > > I know it might seem like we are taking the label too literally but we are > trying to maintain idle capacity for you. The tricky part is since we > always spin up a new idle instance when an existing one begins to serve > traffic it looks like they are sitting around unused when they are in fact > being used often just others immediately take their place. Are you sure > this is not the behavior your are observing? > > Thanks, > > Greg > > On Wed, Mar 14, 2012 at 8:00 AM, Jeff Schnitzer <[email protected]> wrote: >> >> On Wed, Mar 14, 2012 at 4:28 AM, Tapir <[email protected]> wrote: >> > >> > On Mar 14, 1:17 pm, Gopal Patel <[email protected]> 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 [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. >> > > -- > 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. -- 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.
