We may have to get someone from GOOG to weigh in. Requests have a 60s time limit, but from testing it seems that Initialization has a 15s limit. I don't know if this is a bug, a feature, or a flaw in my testing.
Also my "best practices" doesn't guarantee to fix everything, there could still be a bug, but I was hoping that be eliminating the obvious causes we might get closer to resolution. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Alexis Sent: Monday, January 16, 2012 1:30 AM To: Google App Engine Subject: [google-appengine] Re: Why are several production issues related to DeadlineExceededErrors being ignored? Thanks for the shot! Here are some comments: - isn't the limit 60sec instead of 15sec? - We indeed have the pending latency slider set to default, but out of our 12 instances we have 3 resident ones, so the slider will have little effect on our application's performance. - Requests that DEE typically have this signature: ms=63498 cpu_ms=1097 api_cpu_ms=0 cpm_usd=0.030639 loading_request=1 pending_ms=373 exit_code=104 So it did not spent much time waiting to be served... And the DEE is raised during the import phase. - Our warmup requests, that import most of our modules then return a simple "ok" string, take in average 2100ms to complete (min 860, max 3800). But during DEE spikes they can also raise DEE. -- 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. -- 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.
