Thanks for your suggestion. I will take a look at the appstats one more time. What I am noticing though is api_cpu under 500ms (and many much below that) but sometimes overall cpu overshoots 700 ms. More over, for request aborted error messages, it doesn't really look like the service is even called - overall cpu in those instances is over 10000 ms but api_cpu is 0 ms. Am I interpreting this right?
I have seen old posts where users recommended a cron and I tried that out today with surprisingly positive results. Other than this potentially causing few instances to stay alive, I can't think of any other explanations. Any one why that is better? In any case, I wonder if that is going to really help if concurrent requests increase and demand more active instances. Thanks. On Mon, Oct 4, 2010 at 6:30 PM, Julian Namaro <namarojul...@gmail.com>wrote: > > Hi, > > > as a GAE developer, is there anything that we can > > do to avoid "Request aborted error" scenarios? > > You can run appstats, and if your app has any request taking more than > ~700ms work on optimizing it. Long requests are the first to time out > during periods of high latency and are generally a source of problems > in App Engine. > > -- > 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-appeng...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com<google-appengine%2bunsubscr...@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-appeng...@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.
