Yea, I'm working on a communication layer for pyodbc or pypyodbc which will handle requests with gevent, thus your application should yield properly, but it's not available just yet, and it won't necessarily be a drop-in replacement for pyodbc though. In the meantime, this is usually good enough, and you can set timeouts for the queries and connects, but that would be a change to the DAL.
On Wednesday, November 6, 2013 4:50:33 PM UTC-7, Niphlod wrote: > > > > On Thursday, November 7, 2013 12:23:06 AM UTC+1, Derek wrote: >> >> Ah, if you are on Windows, I would recommend you run it with gevent >> instead of rocket, it should be faster than even apache. >> >> unfortunately it doesn't work as happily as it should: if you're using > any non-green module (he's working with mssql, hence either pyodbc or > pypyodbc, that are not), those libraries don't "yield", so you block all > other greenlets in the meantime. > Without an upstream proxy balancing to multiple gevented web2py(s) if you > have a "blocking" query to the database you queue up basically all other > connections. I guess that without an apache ProxyBalancer (or a much > yummier gunicorn, as it stands due in two > months<https://github.com/benoitc/gunicorn/issues/524>) > those web2py windows apps with non-green modules will run more > "concurrently-friendly" with any "old" threaded webserver. > > -- 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/groups/opt_out.
