Every efficiency trick brings down considerably the response time, but 
usually you'd start from  < 400 ms response times to go lower, maybe 
arriving at < 100 ms

2 full seconds is so much that it's not web2py the one you should look 
at.... it's your app's code.


-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to