Thomas Moreau <thomas.moreau.2...@gmail.com> added the comment:

This behavior results from the fact that in 3.6, the result_queue is used to 
pass messages to the queue_manager_thread. This behavior has been changed in 
3.7 as we rely on a _ThreadWakeup object.

In 3.6, when the result_queue is filled with many large objects, the call to 
result_queue.put(None) will hang while the previous objects are being handled 
by the queue_manager_thread, causing a latency in the submit.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue33945>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to