[issue33945] concurrent.futures ProcessPoolExecutor submit() blocks on results being written

2018-06-28 Thread Daniel Barcay
Daniel Barcay added the comment: Just got the drop of the python3.7 release. I can confirm that this is fixed in python3.7 in my workload. Nice job! Thanks for changing the mechanism of thread-sync. I'm grateful. -- resolution: -> fixed stage: -> resolved status: open -&g

[issue33945] concurrent.futures ProcessPoolExecutor submit() blocks on results being written

2018-06-22 Thread Daniel Barcay
Daniel Barcay added the comment: adding experts bquinlan and pitrou for concurrent.futures to nosy-list as per bug tracker directions. -- nosy: +bquinlan, pitrou ___ Python tracker <https://bugs.python.org/issue33

[issue33945] concurrent.futures ProcessPoolExecutor submit() blocks on results being written

2018-06-22 Thread Daniel Barcay
Daniel Barcay added the comment: Line number was incorrect due to local edits. Correct line number is process.py:L464 "self._result_queue.put(None)" -- ___ Python tracker <https://bugs.python.o

[issue33945] concurrent.futures ProcessPoolExecutor submit() blocks on results being written

2018-06-22 Thread Daniel Barcay
New submission from Daniel Barcay : I have tracked down the exact cause of a sizable performance issue in using concurrent.futures.ProcessPoolExecutors, especially visible in cases where large amounts of data are being copied across the result. The line-number causing the bad behavior