Hi, Jesse Noller <jnoller <at> gmail.com> writes: > If python were to have free threading, courtesy of a lack > of the GIL, it would help those people quite a bit. Sometimes you just > need shared state. Myself? I used multiprocess *and* threads all the > time for various reasons. I think it is important to remind that the GIL doesn't prevent (almost) true multithreading. The only thing it prevents is full use of multi-CPU resources in a single process. But if you are using threads to reduce latencies rather than increase throughput, the GIL isn't really an obstacle (it probably makes things a bit worse than a free-threading scenario, but not that much; and you can tweak sys.setcheckinterval()). Regards Antoine.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4