I don't think so. You just put the X requests into the queues for the N instances already running. This gives you additional latency for the X requests, of course - it's not free - but if the latency added is less than the instance startup time, then it's a better solution than what we have. In my own case, the queue length for existing instances is never greater than 1 or 2, and the average latency per request is about 200ms, while instance startup is 10s. The math in my case is pretty simple: it's hardly ever really worth spinning up a 2nd instance, but GAE does it pretty frequently.
Someone should craft a Google Code Jam problem based on this issue. - Kris On Thursday, May 23, 2013 11:55:11 AM UTC-7, Tom wrote: > > I'm not that experienced with GAE, but I'm wondering whether it really is > that simple. If an instance of my app takes 10s to start up, and my app > can, at peak, receive X requests in a 10s period, then wouldn't I require > close to X idle instances running all the time to satisfy your criteria. > And wouldn't that be prohibitively expensive for most apps? > > >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
