This may be related to GAE storing sessions in database.

On Jun 24, 11:00 am, Carl <[email protected]> wrote:
> thanks. I saw -F PROFILER_FILENAME in the documentation and noted that
> it didn't work on GAE (because -F is file based)
>
> For GAE, Google recommend (and provide) an alternative main()
> function.http://code.google.com/appengine/kb/commontasks.html#profiling
>
> Using this and running on GAE produces curious output.
> GAE logs displays (in red) 1400cpu_ms & 129api_ms indicating that my
> page is too heavy. And yet the 'GAE' profiler quotes 19500 function
> calls in 0.245 CPU seconds (the page doesn't do much so perhaps .245
> is too heavy!)
>
> Running locally, using -F, the same page records 9500 function calls
> taking .207 CPU seconds. So that's 10K fewer function calls between
> local and GAE.
>
> On Jun 24, 2:05 pm, mdipierro <[email protected]> wrote:
>
> > try web2py.py -h
> > there is a profiling flag but does not work on GAE
>
> > On Jun 24, 4:03 am, Carl <[email protected]> wrote:
>
> > > hi
>
> > > Is there a section covering profiling Web2Py projects?
>
> > > I'm using GAE and found this from google which are generic
> > > instructions for any Python 
> > > code:http://code.google.com/appengine/kb/commontasks.html#profiling
> > > [this requires me to modify the framework file gaehandler.py]
>
> > > I wondered if there was anything formalised for Web2Py?
>
> > > Back in Feb, there was a thread discussing code 
> > > changeshttp://groups.google.com/group/web2py/browse_thread/thread/8e38fc1c17...
> > > but I can't find anything more structured (I'm probably not looking in
> > > the right place!)
>
> > > thanks
>
> > > Carl
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py Web Framework" 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/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to