yep...thread implementation of python 2.x sucks..so try to avoid threads. use multi process for cpu intensive tasks and async IO or coroutine for io tasks.
w*g
7 楼
not necessary, think the situation: you want to hire a full professor, generally you need to give him/her tenure . how do you know this guy is not a nasty person. consequently, you will be hesitating to give the tenure directly unless you know the guy very well. for assistant professor, you will not be that concerned because no tenure decision involved.
Thanks! And GIL is still there in CPython 3.1. I hope the problem will be solved soon.
【在 d***q 的大作中提到】 : yep...thread implementation of python 2.x sucks..so try to avoid threads. : use multi process for cpu intensive tasks : and async IO or coroutine for io tasks.
b*d
10 楼
要求不一样.
p*o
11 楼
GIL in CPython is likely to exist forever. 积重难返
【在 l*********8 的大作中提到】 : Thanks! : And GIL is still there in CPython 3.1. I hope the problem will be solved : soon.
f*y
12 楼
it sounds reasonable.thanks
tenure well.
【在 w******g 的大作中提到】 : not necessary, : think the situation: : you want to hire a full professor, generally you need to give him/her tenure : . how do you know this guy is not a nasty person. consequently, you will : be hesitating to give the tenure directly unless you know the guy very well. : for assistant professor, you will not be that concerned because no tenure : decision involved.
d*q
13 楼
Because python use reference-counting so it would be quite hard to remove GIL completely. If you are really care about this issue there are two options: 1: you may try pypy & its experimental module: STM it is said that STM has already worked with multi cores directly. However it is far away from production usage. 2: use other implementations like Jython, IronPython or event other languages..
【在 l*********8 的大作中提到】 : Thanks! : And GIL is still there in CPython 3.1. I hope the problem will be solved : soon.