Hi,

I'm using web2py in a project that stands on top of a REST api. The project 
is write intensive (around 110k requests a day, with all the requests 
making at least 2 updates to the datastore).
All my requests seems to uso at least 200 cpu_ms (even dummy requests that 
only places a item on the queue to be processeced later). Is this behaviour 
right? I used to get around 20 cpu_ms while using django with the same 
application (I'm currently re-writing it on web2py).
Is there some way to optimize web2py for a appengine deploy (I already 
followed all the documentation)

Thanks!

-- 



Reply via email to