On Oct 2, 4:07 pm, Alexander Konovalenko <[email protected]> wrote:
> On Fri, Sep 30, 2011 at 13:13, Tapir <[email protected]> wrote:
> > If "Max Idle Instances" == 1, then there will be only one idle
> > instance.
> > This instance will restart every some minutes.
> > If a visit comes when this instance is restarting, slow page loading
> > occurs.
>
> > It seems the current scheduler implementation is "showdown the old
> > instance firstly, then create a new one".
> > If the scheduler firstly create and initialize the new one, then
> > shutdown the old one, slow page loading problem will go.
>
> If I understand correctly, you have tested it so this is not
> theoretical. It looks like this would be a good issue to file in the
> issue tracker. Could you please post a link to the issue here when you
> file it?
>
> Do you have Always On enabled? I wonder how often does the instance
> restart. How many requests does it handle between restarts? Are there
> any time periods when there are no instances or more than one
> instance?
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.
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.


>
>  -- Alexander

-- 
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.

Reply via email to