Currently the exhaust script generates a set of tasks that are handled by the multiprocess.Pool library. The library handles all the management related to the task executions, and it is not clear whether the task is assigned to one CPU core and one only, but it seems this is not the case.

To have more robust performance results in terms of runtime, it would be worth locking each task that is being executed to one CPU core only, not allowing the task to be moved across different cores until it is finished.