"We decide to schedule additional instances of your app based on its user-facing latency. "
This very material fact is not even mentioned in the article 'Best practices for writing scalable applications' http://code.google.com/appengine/articles/scaling/overview.html johnP On Sep 16, 9:03 am, Stephen <[email protected]> wrote: > On Sep 16, 4:33 pm, "Nick Johnson (Google)" <[email protected]> > wrote: > > > Hi Stephen, > > > On Thu, Sep 16, 2010 at 4:31 PM, Stephen <[email protected]> wrote: > > > > On Sep 15, 2:33 pm, "Nick Johnson (Google)" <[email protected]> > > > wrote: > > > > Hi, > > > > > We don't throttle apps. > > > > What does 'throttle_code' mean? > > > As I expanded immediately after the one sentence you clipped out of my > > reply, we decide to schedule additional instances of your app based on its > > user-facing latency. > > Yes, I read that. > > But what does 'throttle_code' mean when it appears in your logs? > > http://groups.google.com/group/google-appengine/browse_thread/thread/... > > Does it mean that due to too many requests taking > 1000ms a request > which otherwise would have started a new instance was throttled? If > so, that's useful info. -- 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.
