Parallel Toolbox sets a max of 1 workers on new cluster in R2020b
Afficher commentaires plus anciens
Both R2020a and R2020b exhibit this behavior on our new cluster where you start matlab then do >>parpool(10).
It responds "You requested a minimum of 10 workers, but the cluster "local" has the
NumWorkers property set to allow a maximum of 1 workers"
There are 94 cores available to jobs on each node.
In the Environment / Parallel / Create and Manage Clusters, NumWorkers is left blank which is the default setting of number of cores. The difference with this cluster is that Matlab is built on a VM and not on a compute node, like the older one
Our older cluster responds with:
Connected to the parallel pool (number of workers: 10).
ans =
ProcessPool with properties:
Connected: true
NumWorkers: 10
Cluster: local
AttachedFiles: {}
AutoAddClientPath: true
IdleTimeout: 30 minutes (30 minutes remaining)
SpmdEnabled: true
6 commentaires
Raymond Norris
le 5 Nov 2020
What does
feature numcores
return?
Christopher S Reidy
le 5 Nov 2020
Raymond Norris
le 14 Nov 2020
Some more follow-up. Are you running MATLAB
- on Windows, Linux, or Mac?
- via a scheduler (e.g. Slurm)?
- from within cgroups?
- on a Superdome Flex Server?
Walter Roberson
le 14 Nov 2020
The output showd glnxa64 so it must be Linux.
I would suggest checking the environment variables to see if they are telling matlab to use only one core.
Christopher S Reidy
le 16 Nov 2020
Christopher S Reidy
le 16 Nov 2020
Réponse acceptée
Plus de réponses (0)
Catégories
En savoir plus sur Third-Party Cluster Configuration dans Centre d'aide et File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!