3 ms·
So after this and some follow-on work, you can switch from multiprocess message passing parallelism to same-process message passing multi-interpreter parallelis
by fulafel 4y ago
So after this and some follow-on work, you can switch from multiprocess message passing parallelism to same-process message passing multi-interpreter parallelism? Which would decrease message passing overhead at cost of crash/memory safety isolation.
- bratao 4y agoYes, that what I´m excited about. A ThreadPoolExecutor like implementation that effectively use multiple CPUs.
- fulafel 4y agoThreadPoolExecutor seems to be a concept from Java land which is pretty different, you can share objects between Java threads.
- fulafel 4y agoReplying to myself, there's also a identically named class in Python nowadays. But the point remains, you won't get that type of shared-memory parallel multithreading from this. (Which is good I think as I'm a fan of Erlang style message passing parallelism)