Your app: /showsort/list 500 41106ms > /showsort/list 500 29590ms > /showsort/list 500 40991ms > /showsort/list 500 40340ms > /showsort/list 500 30155ms > /showsort/list 500 35481ms > /showsort/list 500 40109ms > /showsort/list 500 42148ms > > /showsort/list > com.google.apphosting.api.DeadlineExceededException: This request > (675bc7926055c7e2) started at 2009/09/04 21:33:38.750 UTC and was still > executing at 2009/09/04 21:34:07.223 UTC
You are exceeding the 30s request deadline with prejudice on every single request to /showsort/list. Your app gets terminated each time, which causes it to have to be reloaded from scratch for subsequent requests. App reloads can be expensive (and it appears that yours are), and that seems likely to be the root cause behind the warnings you're receiving about excessively high latency. In terms of quota, the warning is specifically describing your "simultaneous active request limit", not long-term quota like CPU time or datastore usage. On Fri, Sep 4, 2009 at 3:56 PM, Xlorep DarkHelm <ch...@darkhelm.org> wrote: > > Request deadline? I've not been exceeding any request deadline. I'm > getting this a lot now: > > # > > 1. > 09-04 12:01PM 00.892 /showsort/list-- 500 10455ms 0cpu_ms 0kb > Mozilla/5.0 (en-us) AppleWebKit/525.13 (KHTML, like Gecko) Version/3.1 > Safari/525.13,gzip(gfe) > See details > > 72.14.192.66 - - [04/Sep/2009:12:01:11 -0700] "GET /showsort/ > list-- HTTP/1.1" 500 0 - "Mozilla/5.0 (en-us) AppleWebKit/525.13 > (KHTML, like Gecko) Version/3.1 Safari/525.13,gzip(gfe)" > "showsort.appspot.com" > > 2. > W 09-04 12:01PM 11.348 > > Request was aborted after waiting too long to attempt to service > your request. Most likely, this indicates that you have reached your > simultaneous active request limit. This is almost always due to > excessively high latency in your app. Please see > http://code.google.com/appengine/docs/quotas.html for more details. > > > ----------------------- > > the problem with this is when I check my Quota page, I'm way, WAY > below my limit. There are only two things that show any sign of being > used by the quotas: > > CPU Time 4% 0.27 of 6.50 CPU hours Okay > > Deployments 2% 6 of 250 Okay > > Everything else is at 0%. > > My requests are: > > Requests 0% 201 of 1333328 Okay > > > If I've reached my "simultaneous active request limit", somehow... > where would I even be able to see that? I'm thinking that's a false > alarm. Especially as my app really is not that taxing, at all. The > vast majority of the processing for it (the graphics/UI processing) is > done through GWT on the client side. > > > On Sep 4, 11:57 am, Toby Reyelts <to...@google.com> wrote: > > Unfortunately, when you exceed the request deadline, you can lose your > logs > > for that request. I would suggest paring your RPC down to the very bare > > minimum, so that you're not exceeding the deadline, then adding in logic > and > > logging timings as you go. You should then be able to narrow things down > to > > the slow operations which are causing you problems. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
