Adam, The reason this is happening is because your requests take too long to execute. App Engine apps will autoscale if they are generally kept as low latency requests. The average latency of your requests is 10000ms, so we will not add instances. You will need to reduce the latency of your user facing calls to under 1000ms (we recommend 800ms, and 400ms) for best performance.
Strategies to do this: - denormalize your data model to emphasize reads - move long running jobs to task queues Your web/user facing requests must be as fast as possible. -- Ikai Lan Developer Programs Engineer, Google App Engine Blogger: http://googleappengine.blogspot.com Reddit: http://www.reddit.com/r/appengine Twitter: http://twitter.com/app_engine On Wed, Oct 20, 2010 at 3:17 PM, Adam Johnson <[email protected]>wrote: > Hi folks, > > I'm getting tons of this error on my app id 'ipadsocial' yesterday and today. > Could you take a look? Maybe you should increase some of the internal quotas > for my app. It is paid app. > > Thanks, > Adam > > "Request was aborted after waiting too long to attempt to service your > request. This may happen sporadically when the App Engine serving cluster is > under unexpectedly high or uneven load. If you see this message frequently, > please contact the App Engine team." > > -- > 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]<google-appengine%[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.
