Thanks Massimo. So what're the pros of having multiple threads in the context of web2py, if any? Asynchronous processing?
On Monday, 18 June 2012 15:19:03 UTC-4, Massimo Di Pierro wrote: > > There are pros and cons. If you use threads in a python program, the more > computing cores you have, the slower - not faster - the program gets. This > is a python feature because even if you have threads, there is only one > interpreted and therefore execution is serialized anyway. For scalability > you should have processes (not threads) one per core. > > On Monday, 18 June 2012 11:34:39 UTC-5, mrtn wrote: >> >> >> I'm deploying web2py with uwsgi 1.2.3, and upon starting the app, there >> is message in the uwsgi log says; >> >> *** Python threads support is disabled. You can enable it with >> --enable-threads >> *** >> >> And in the uwsgi doc, it says the following for option enable-thread: >> >> Enable threads in the embedded languages. This will allow to spawn >> threads in your app. >> >> I wonder if I really need this enabled for web2py. If so, what would be a >> common use case for it. Thanks. >> >> >>
