Inada Naoki <songofaca...@gmail.com> added the comment:
Current default value is decided in here: https://bugs.python.org/review/21527/#ps11902 It seems there were no strong reason for current cpu_count * 5. I think cpu_count + 4 is better default value, because: * When people are using threadpool for CPU heavy job which releases GIL, workers >= cpu_count is good. * When people are using threadpool for multiplexing I/O, best workers number is vary on the workload. But I think 4~16 is good for typical case. > This is amplified by the fact that the > `concurrent.futures.ThreadPoolExecutor` threads are never killed, and are not > re-used until `max_workers` threads are spawned. Note that this is fixed by #24882. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue35279> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
