Some ideas:

There is a log_stats decorator in gaehandler.py that can be
uncommented and enabled in production to give a more precise timing
profile than the log coarse timing.

The main caching mechanism is in compileapp.py and the compiled code
should be cached in a dict called 'cfs' which can be printed for
debugging.

If the caching mechanism is working, and the responses are not fast
enough, then memcach'ing the responses could be used to reduce
database accesses.

Robin



On Apr 14, 2:38 pm, Ted G <tedg...@gmail.com> wrote:
> I'm wondering if anyone has tips on where I should start in trying to
> track down performance problems running my web2py application on GAE.
> Initially I created an application using only the api's supplied by
> GAE. This app was very fast in terms of response times.
>
> I've since recreated and updated the app within web2py and have been
> frustrated with very poor performance. I experience long delays when
> loading pages and in particular, when loading pages that contain small
> images (where the image source is using web2py's download() handler to
> retrieve an image stored in the db as a web2py upload field).
>
> As mentioned, my previous GAE API version of the app also stored these
> same images as blobs in the db, but experienced none of the
> performance issues I see under web2py.
>
> Due to the delay experienced loading pages, my first thought, after
> reading threads in this group, was that maybe my code was being
> recompiled on every request. I updated to 1.61 this morning in the
> hope that the GAE cache issue it was addressing would solve my problem
> - but running a side to side comparison between a  1.59 version and
> 1.61 on GAE I did not see any difference.
>
> Any tips on how I can narrow down the source of the performance
> problems would be greatly appreciated.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to 
web2py+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to