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. Another option is to add a virtual filesystem on appengine, and cache the code as .pyc files.
Robin On Oct 17, 8:26 pm, justinjas <[EMAIL PROTECTED]> wrote: > I just started playing around with web2py and setup a very basic app > that merely displays the ip address of the visitor > (ipaddresstoday.com). The problem I'm having is that every request is > going over the allotted cpu cycles for an request in app engine. > > For example in my logs on app engine I always see this. > > 10-17 11:58AM 01.591 / 200 817ms 2765mcycles 0kb > > With the mcycles highlight in red because they are over allocation. > Also as you can see the response time is fairly slow at 817ms. I know > in general GAE has some restrictive limits but is this the norm for > web2py in app engine? Anyone else running on this platform and have > some good numbers to show. > > I just want to make sure before I pick a framework to go with that it > will work in app engine without issue. > > Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
