OK - here's what I see. The script ran two out of two times successfully with AppStats (of course). There are many, many rdbc and AdWords API calls. However, the longest real time spent was on a single AdWords API call for 60 seconds. Here's some of the readout:
> service.call #RPCs real time > rdbms.Exec 1004 78364ms > urlfetch.Fetch 721 266851ms > rdbms.CloseConnection 497 7027ms > rdbms.OpenConnection 497 7599ms > rdbms.ExecOp 491 48623ms > logservice.Flush 10 41ms > memcache.Set 1 6ms > memcache.Get 1 7ms And here was the log info from AppStats on the long AdWords API call: > @576702ms urlfetch.Fetch real=59837ms api=0ms cost=0 billed_ops=[] > Request: URLFetchRequest<Method=2, > Url='https://adwords.google.com/api/a.../v201306/AdGroupCriterionService', > ...> > Response: URLFetchResponse<> On a side note, it was a little interesting getting AppStats to work on my module. At first I had a 404 error when attempting to access the admin panel. My working code included: 1. A custom handler for the appstats ui in my (backend/ non-default) module .yaml that included a URL that matched the regex pattern sending URLs to my module in the dispatch file. 2. Renaming my webapplication to "app" from "application". I had named my backend WSGI application "application" and noticed I wasn't picking up the appstats when running. 3. Adding the appengine_config per documentation. 4. The first time I successfully ran the script with appstats I got an "Invalid or stale record" error when trying to view the timeline. I made no changes, waited about an hour, then reran the script and it worked... Will On Friday, November 8, 2013 8:34:34 AM UTC-8, [email protected] wrote: > > Thanks for the response. I'm running a B8 and I've run AppStats on these > call in the past. I'll run it again and post the log to see if there's > anything interesting there. > > Thanks for the help! > > Will > > On Thursday, November 7, 2013 2:57:07 PM UTC-8, Vinny P wrote: >> >> On Thu, Nov 7, 2013 at 11:06 AM, <[email protected]> wrote: >> >>> I believe it's hanging when I'm calling AdWords apis (I have tried >>> breaking these calls up a bit, waiting a little between batches, not >>> caching the urlfetch) but I lose some of the logging when I get this error >>> and can't seem to figure out if there are local variables eating up all the >>> memory or if I need to continue to break up the api calls.Is there any way >>> to help me diagnose? >>> >> >> >> To inspect the urlfetch calls to Adwords, you can install AppStats ( >> https://developers.google.com/appengine/docs/python/tools/appstats ). If >> those calls are hanging, you'll see it in the performance report. >> >> As for the memory issues, try increasing your application's instance >> class; i.e. if you're currently using a B1 sized module, try going up to B2 >> for a day and see if it fixes the problem. Of course, this is just a >> temporary band-aid until the memory-hog can be found. >> >> >> ----------------- >> -Vinny P >> Technology & Media Advisor >> Chicago, IL >> >> App Engine Code Samples: http://www.learntogoogleit.com >> >> > >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
