f0ad37e3cd
Currently max_threads defaults to 5 * (number of CPU cores). Because ThreadPool is created in each worker, and max_workers defaults to (number of CPU cores), the total number of threads is by default 5 * (number of CPU cores) * (number of CPU cores) . In case a node has 24 cores CPU, orchestrator may launch 2880 threads at maximum, which is too large. (Note that it may even launch doubled number of threads due to separate workers for rating processing and reprocessing). Lower down the default max_threads, by getting rid of the factor dependent on number of CPU cores, to have reasonable cap by default. Change-Id: I0efbf6b9e5331acc0d9f334cbbe6bebeecc5722a Signed-off-by: Takashi Kajinami <kajinamit@oss.nttdata.com>
6 lines
156 B
YAML
6 lines
156 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
The ``[orchestrator] max_threads`` parameter now defaults to 16, to avoid
|
|
too many threads in total in node with many CPU cores.
|