4 ms·
Only for computationally expensive operations done in interpreted Python. C extensions, IO operations etc. always release the lock. In practice GIL is a proble
by dullgiulio 9y ago
Only for computationally expensive operations done in interpreted Python.
C extensions, IO operations etc. always release the lock.
In practice GIL is a problem only when it is profiled to be a problem.
Python is used a lot in the data analysis world and nobody cares about the lock, because a fraction of the CPU time is spent within the lock.
- amelius 9y ago> Only for computationally expensive operations done in interpreted Python. C extensions, IO operations etc. always release the lock. So you are saying it is a problem in Python but not in other languages? Which is exactly my point :)