In compileapp.py, after reading, parsing, and compiling a model, view, or controller, if a .pyc cannot be written to disk, instead store the compiled code, by file name/function, in a global dict so that next request you can simply load the precompiled code directly from RAM.
Since web2py does not have an environment (does not distinguish between development and production etc), the only way to update the cached code is to check the mtime of each file on every request which is wasteful in production where the code does not change, but not nearly as wasteful as repeatedly reading, parsing and compiling. Robin On Oct 18, 10:27 am, mdipierro <[EMAIL PROTECTED]> wrote: > On Oct 18, 9:51 am, Robin B <[EMAIL PROTECTED]> wrote: > > > Web2py 'works' on appengine, but it is reading, parsing and compiling > > the models, controllers, and views on *every* request causing all the > > wasted CPU cycles. Normally, web2py caches code as .pyc files, but > > you cannot write the filesystem on appengine so nothing gets cached by > > default. It is trivial to cache the compiled code in a dict and reuse > > it on the next request. > > Could you explain more? --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
