On 14 Mar 2014, at 2:03 PM, Niphlod <niph...@gmail.com> wrote: > So.... seems that web2py shell and python script behaves exactly the same (if > web2py was introducing complexity it should show right there). > The same environment executed by rocket or uwsgi gets some gap (roughly 2x > time). > uwsgi behaves a little better, but not that much (surely in concurrency but > that's another deal). > Every wsgi implementation takes the hit, micro or macro framework. > > Soooo.... maybe the wsgi "environment" is posing some limits ?
Setting aside that your 2x is a lot better than HH's, what's been bothering me (assuming the effect is real) is: what could possibly be the mechanism? Running it with web2py -S eliminates some possibilities, too, relating to the restricted environment stuff. So I'm thinking it must be thread activity. Yappi comes to mind, but not sure how to invoke it in a wsgi environment. -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
