3 ms·
From my own experience, ThreadPoolExecutor is a tarpit for the naieve user (me) -I wound up in multiprocessing_in_dill because serialisation hits you out of the
by ggm 7y ago
From my own experience, ThreadPoolExecutor is a tarpit for the naieve user (me) -I wound up in multiprocessing_in_dill because serialisation hits you out of the blue as an issue. Things can work with pool executor count 1 and fail at 10 and you have no idea why. A map(func, [list]) abstraction should work. It just sometimes doesn't.
I have no doubt better abstraction and core knowledge could get over this, and they are probably traps for the unwary in MP as a whole, not the specific model (been a CS person for 40 years btw, so this is perpetual newb state)