Hi, I'm building an application that needs to write to multiple (sharded) counters per request. Overall, my average response time is ~300ms, but if some other more complex requests happen then it goes over.
The majority of time spent per request is with writing to the datastore for the counters. Unlike CPU cycles spent on datastore operations (http://code.google.com/p/googleappengine/issues/detail? id=814 ), my limited tests show that the time spent there does seem to count against your time average, and that going over 300ms/req consistently results in a a nasty over-quota error immediately upon every request -- and I think it won't even let you replace it with your own canned error template. I looked around the docs and quota pages, and was unable to find anything official in writing regarding this particular limit. Indeed, so far the only from-Google reference I've been able to find that mentions getting cut off for average request times is Guido's talk at DjangoCon (see http://www.youtube.com/watch?v=CmyFcChTc4M&eurl=http://www.technorati.com/videos/youtube.com/watch%3Fv%3DCmyFcChTc4M around 21:20 ). I am wondering if someone can point me to the appropriate docs, or provide more details regarding this 300ms/average watchdog: specifically whether datastore time is indeed meant to count against you, and ideally how 'average' is calculated and whether you can catch the error in your view code (and what the error is called). Cheers, -Josh --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
