The version of web2py in trunk has already been patched to use app stats. http://googleappengine.blogspot.com/2010/03/easy-performance-profiling-with.html
It might help a little. Most likely on GAE it's DBIO that slows it down. On Aug 30, 10:01 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > It is slow. does it contain a lot of code or a lot of DB IO? I cannot > say without looking at the code. > > On Aug 30, 9:09 am, Jurgis Pralgauskis <jurgis.pralgaus...@gmail.com> > wrote: > > > > > Hello, > > > I have my beta apphttp://code.google.com/p/code-by-example/ > > onhttp://web2py-gae-test.appspot.com/ > > > which seems to load quite > > slowlyhttp://ftp.akl.lt/incoming/jurgio/gae-logs.png > > > I also tried logs,http://ftp.akl.lt/incoming/jurgio/cbe.profile.txt > > but don't see big problems (though i use profiling for the first > > time..) > > > *** > > I recently made KEEP_CACHED = True > > > and for Session use Memcache > > as I use session quite a bit > > > but still can't feel that its better > > > *** > > I also see info in logs: > > This request caused a new process to be started for your application, > > and thus caused your application code to be loaded for the first time. > > This request may thus take longer and use more CPU than a typical > > request for your application. > > > ***http://plugins.jquery.com/project/appear > > might help me a bit, > > as mostly used controller shows ~ 20% of what it loads > > > I tried web2py_component(action,target) { > > $('#'+target).appear(function() { > > instead of > > jQuery(document).ready(function(){ > > but this did' t work :( > > > any suggestions ?
