Sorry for the temporary radio silence. I was trying to get an AppStats log for my local machine to compare. Absent that, qualitatively from running this many times I'd say the times are pretty close between local and GAE hosted (even with pretty substantial debug logging locally). The GAE stats came it at 37ms on average and that's got to be about right.
I'm going to attempt to: 1. Break this script down into smaller components and run them sequentially. The hope here is that the garbage collector helps with any monster memory variables. 2. Lower my urlfetch default deadline and explicitly handle url deadline exceeded errors within my adwords batches. The theory here is that GAE is killing jobs that consistently exceed some arbitrary urlfetch deadline independent of what is being set by an individual application. Not necessarily a bad thing. 3. Move these pieces from a module to a Google Compute Engine instance. While it's not ideal working without an explicitly identified issue, I've got to do what I can to get this consistently running. I'm still 50% at best. Thanks again for all your help. Will On Friday, November 8, 2013 8:34:03 PM UTC-8, Vinny P wrote: > > On Fri, Nov 8, 2013 at 5:06 PM, <[email protected] <javascript:>> > wrote: > >> 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. >> > > > If you repeat this AdWords API call from your local machine, does it take > the same amount of time or less? > > > On Fri, Nov 8, 2013 at 5:06 PM, <[email protected] <javascript:>> > wrote: > >> >> 1. 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... >> >> > > Yes, AppStats occasionally needs some time to initialize. Feel free to > leave the AppStats recorder on - it doesn't take up much memory and it > might catch some interesting info sooner or later. > > > ----------------- > -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.
