Proper way to use multiprocessor.Pool in a nested loop
Ideally, you should call the Pool() constructor exactly once – not over & over again. There are substantial overheads when creating worker processes, and you pay those costs every time you invoke Pool(). The processes created by a single Pool() call stay around! When they finish the work you’ve given to them in one part … Read more