On 16 Mar 2014, at 1:31 PM, horridohobbyist <horrido.hobb...@gmail.com> wrote: > Well, I managed to get gunicorn working in a roundabout way. Here are my > findings for the fred.py/hello.py test: > > Elapsed time: 0.028 > Elapsed time: 0.068 > > Basically, it's as fast as the command line test! > > I'm not sure this tells us much. Is it Apache's fault? Is it web2py's fault? > The test is run without the full web2py scaffolding. I don't know how to run > web2py on gunicorn, unless someone can tell me. >
The point of gunicorn (in this context) is to run requests on separate worker processes, one thread per process. It tends to confirm the idea that the underlying problem is related to having other outstanding Python threads in the process that's running your request, as is typical with Apache (and Rocket). You're almost certainly seeing the effect of the GIL. Have a look at slide 2-7: http://www.dabeaz.com/python/NewGIL.pdf -- 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.
