- You are oversubscribing the number of actual compute cores in your machine. Each one of the extra workers is now consuming additional RAM, which still being bottlenecked by the number of compute cores for compute operations. So you may be consuming more resources than you really need to, and not getting any additional performance from doing so.
- You may actually make performance worse if your system has to use things like virtual memory/swap to support the extra workers, which can slow down system performance overall.
Qustions about number of workers in parpool
65 visualizaciones (últimos 30 días)
Sandra Martinez el 9 de Jun. de 2021
I'm trying to extend the number of workers when using parpool (my computer has a total of 16 cores and 32 threads)
If I do:
I recived an error message
If I change by;
myCluster = parcluster('local');
I can use now 30 workers. It is correct the way I'm changing the number of workers? Is there any danger doing in this form?
Jason Ross el 9 de Jun. de 2021
The default for number of workers is set to the number of actual cores you have in the system, not threads. As you have found, it is overridable. This is one way to do it, the other ways are to set is as the default in Settings, or in the Local cluster profile.
Risks from doing this:
The default was set as a default based on the anticipation that most operations people would be doing with MATLAB were math-heavy and using the compute cores, and threads were not of much use.