+1 On Jun 2, 11:19 am, dloomer <[email protected]> wrote: > I've been seeing increased DeadlineExceededErrors, and suspecting that > it's an issue outside of my app but not sure. I'm not sure if a three- > post thread of somewhat similar experiences proves anything or not; > when you refer to "the increasingly poor datastore performance" is > this something that's documented elsewhere and/or acknowledged by > Google? I haven't been able to find anything so far indicating a bona > fide known issue, but maybe I'm not looking in the right place. > > On Jun 1, 9:21 pm, Brandon Thomson <[email protected]> wrote: > > > > > Yes, we are also seeing this. Usually the call at the end of the > > traceback is something related to the filesystem. I think this is > > caused by the increasingly poor datastore performance. > > > On Jun 1, 6:16 pm, Dave Peck <[email protected]> wrote: > > > > Hi, > > > > In the past week, I've seen an alarming number of DeadlineExceeded > > > exceptions on cold hits to my applications. > > > > Most of the stack traces are shallow -- things blow up well before my > > > code is hit. Seehttp://pastie.org/988269forastack trace. > > > > The `bootstrap.py` file is more-or-less a direct copy of the `main.py` > > > from Rietveld. > > > > Can someone on the App Engine team please point me in the right > > > direction here? This is a big change in GAE's behavior in the past > > > week, and it is affecting many of my applications (citygoround which > > > has been in production for half a year; code-doctor which is under > > > development, etc.) > > > > Cheers, > > > Dave Peck- Hide quoted text - > > > - Show quoted text -
-- 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.
