Make sure you have edited app.yaml skipfiles section to upload .pyc (it will skip upoading .pyc by default).
On the most trivial app it takes 12ms with no caching, and using RAM caching I can get 3ms. Robin On Oct 19, 3:30 am, mdipierro <[EMAIL PROTECTED]> wrote: > Justin, this is fantastic, > > I think we are learning something here: > > 1) GAE takes 912-16=896ms to import and bytecode compile the gluon/ > *.py modules and takes 16ms to execute the models/views/controllers. > > 2) GAE can cache the former pyc files when requests/seconds is above > some threshold. > > I think this is good news. We may not need to change anything. > > Robin, what do you think? > > Massimo > > On Oct 18, 11:34 pm, justinjas <[EMAIL PROTECTED]> wrote: > > > Hey Massimo, > > > I still get the same 2000mcycles+ with 800ms+ times. > > > 10-18 08:48PM 27.724 / 200 912ms 2130mcycles 0kb > > > Of interest though is if I refresh the page quickly I can get fast > > responses back from app engine. > > > 10-18 08:48PM 30.007 / 200 16ms 22mcycles 0kb > > > As if app engine is doing their own code caching separate from pyc > > files. > > > Another thing I've notice is that on the slow requests I will see > > these warnings thrown in the logs: > > > no file locking > > no sqlite3 or dbapi2 driver > > no MySQLdb driver > > no psycopg2 driver > > no cx_Oracle driver > > no MSSQL driver > > no kinterbasdb driver > > unable to import dbhash > > unable to import py_compile > > unable to import wsgiserver > > URL rewrite is on. configuration in route.py > > no cache.disk > > > But when the fast load happens on refresh there is only one error: > > > no cache.disk > > > -- > > Justin > > > On Oct 18, 11:05 pm, mdipierro <[EMAIL PROTECTED]> wrote: > > > > Hi Justin, > > > > could you do a test for us: > > > > 1) edit gluon/compileapp.py and comment > > > > if data[:4]!=imp.get_magic(): > > > raise SystemError, "compiled code is incompatible" > > > > 2) run web2py locally, without appengine and "compile" your app > > > > 3) deply on the appengine and see if it works and tell us what timing > > > you get. > > > > Massimo > > > > 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 -~----------~----~----~----~------~----~------~--~---
