with with "Max Idle Instances" set as 1 instead 3. The user experience is better now. ^_^
On Sep 30, 7:25 am, Tapir <[email protected]> wrote: > and with "Max Idle Instances" set as 3. > > There MUST be a bug in gae instance scheduler. > If it is not a bug, it MUST be a bad implementation. > > After some researches, I find If there is only one instance is > running, > the scheduler always avoids using it to handle a new coming request, > even if the idle instance is idling. > Instead, the scheduler always tries to open a new instance to handle > the new coming request. > As a result, the visitor must wait 15s to load the page. > > This problem is intolerable specially for websites with very small > traffic. Almost very visit will wait for 15 seconds. > > How a good scheduler should do? > 1. always use the current idle instance if it is available. > 2. at the same time, create a new instance for potential new > concurrent requests. > It is just that simple. -- 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.
