Hi Stephen,

The scheduler doesn't wait until an instance is needed to start one up
because the startup times are often very long (up to 10s of seconds) so if
it waited until a new instance was actually needed, it would be too late.
 This is partly why we have a scheduler, it takes these things into account
(number of requests in the queue, min pending request time, typical startup
time, etc) to determine when instances are needed so that you are always
behind.  That being said, it might guess wrong but you won't pay for the
excess capacity.  If you set max idle instances to a value that is the
largest number of idle instances we will charge you for during any given
minute.  So, our incentive is to make the scheduler better because if we
spin up lots of instances that don't serve any requests, you aren't going to
pay for them.

Let me know if you have additional questions about this,

Greg

On Tue, Sep 6, 2011 at 2:20 AM, Stephen <[email protected]> wrote:

> On Tue, Sep 6, 2011 at 2:46 AM, Mike Wesner <[email protected]> wrote:
> >
> > In order for them to be idle, they must start.  They can either start
> > as a result of a user facing request or a warmup request.  If you
> > don't want your users to suffer the latency or your instance startups,
> > then warmup requests are still relavant.
>
> Does the scheduler react to instance overload or does it try to
> predict and issue a warmup request in advance? If it's the latter, it
> may guess wrong and you will pay for excess capacity.
>
> --
> 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.

Reply via email to