Re:Python stands to lose its GIL, and gain a lot of speed
by chrisseaton on Sunday October 17, 2021 @12:08PM
(#28897451)
Communicating between processes is more expensive than communicating between threads.
[ Parent
| on HN ]
Re:Python stands to lose its GIL, and gain a lot of speed
by TekMol on Sunday October 17, 2021 @12:16PM
(#28897503)
Ok, but what is the use case where you need high bandwidth inter-thread/process communication?
Re:Python stands to lose its GIL, and gain a lot of speed
by moron4hire on Sunday October 17, 2021 @12:27PM
(#28897597)
Games. Simulations. Backend servers for shared editor experiences. Teleconferencing.
Re:Python stands to lose its GIL, and gain a lot of speed
by chrisseaton on Sunday October 17, 2021 @12:30PM
(#28897626)
Except for embarrassingly parallel problems, the trade-off of generating more parallelism is usually needing finer-grained communication. Canonical examples in the literature are matrix multiplication, triangulation, and refinement.
Re:Python stands to lose its GIL, and gain a lot of speed
by Spivak on Sunday October 17, 2021 @01:10PM
(#28897942)
Large shared state is basically always the answer. You can cop-out and say use a database or Redis if that’s fast enough but that’s just making someone else use many threads with shared memory.
Re:Python stands to lose its GIL, and gain a lot of speed
by adgjlsfhk1 on Sunday October 17, 2021 @12:44PM
(#28897732)
matrix multiply is an obvious one. partial differential equations are another. Sorting is one if you don't care about math.