Hi
> My app traffic is very small now. This is the pain.
> I just found the scheduler doesn't restart the idle instance
> automatically, or doesn't restart the idle instance when the instance
> is idle.
>
Instead, it restarts the idle instance when a visit comes. This is so
> bad. It will make the just coming visit wait for more than 10 seconds.
>
This is correct behaviour as documented, and extensively discussed over the
last few months.
Currently if you are an always on customer
In the application settings you have two sliders, min idle instances and max
idle instances.
Min idle instances sets the minimum number of idle instances that will
always be present.
Once the new billing is in place, you will get a min idle instances slider.
> In the issue I filed, I suggest the scheduler should prepare a new
> instance before shutdown the old idle instance. This way, there will
> always an idle instance for coming requests.
>
> This isn't an issue. I really think you need to reread all of the current
documentation and discussions in this area, as you
are definately misunderstanding the intent of max idle instances.
Also you need to do something about your 10sec startup time or pay for idle
instances ("always on" at the moment)
Tim
>
> >
> > -- Alexander
--
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/-/jvwuOwuZq0oJ.
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.
