Answers below: On Sat, Sep 3, 2011 at 6:12 PM, zdravko <email.workbe...@gmail.com> wrote:
> Just how long does it take to fire up a brand new instance? > That all depends on how long it takes to load up your code, if you are using large frameworks this could take longer, I believe there is a 30s deadline on this, so no longer than 30s. > And, did anyone explain why they are kept spinning for 15 minutes > after any activity? > Mostly because it can take a long time to start an instance, so it is better to keep one running than start a new one for traffic. If you get 2 requests in quick succession and you have no instances running, it could be a long time to wait to service the first request and even longer to wait until the second. > Why is number of idle instances not used to determine how fast they > are brought down? > It is one of the pieces of information the scheduler uses to determine when it is okay to take down an instance. Min and Max Idle Instances are also parameters it takes into account. > Finally, why are internal app processes started and stopped as needed > without interfering with the front end? > I'm not sure I understand this question. Could you elaborate? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > 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 google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
