You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the difference between concurrent.futures.ThreadPoolExecutor and gevent.threadpool.ThreadPoolExecutor?
Will gevent affect the child threads started by the concurrent.futures.ThreadPoolExecutor?(In other words, have the child threads started after monkey patch all also been patched?)
How to determine if the current thread is affected by gevent?
The text was updated successfully, but these errors were encountered:
My general understanding of this is you should continue to use concurrent.futures.ThreadPoolExecutor for IO-bound threads--so long as threading is patched it will use greenlets instead of threads in the threadpool. In principle the underlying Queue and synchronization primitives (e.g. Semaphore) are patched to, so it should "just work"
Whereas, if you are using ThreadPoolExecutor for CPU-bound threads it won't work cooperatively with greenlets, so such code should be replaced (or patched) to use gevent's ThreadPoolExecutor.
Description:
Some question
The text was updated successfully, but these errors were encountered: