why it takes so long for starting parallel pool (parpool) ?

I ran the code in the Linux sys, and it still "Starting parallel pool (parpool) using the 'bcmmjs' profile " after one night.

The only reason I can imagine is,

there are 50 workers in the 'bcmmjs' profile, and I've ran a instant with " pool=parpool('bcmmjs',40);", but it only uses 10 workers actually.

So, when I ran another instant with the same setting (namely " pool=parpool('bcmmjs',40);"), it only output "Starting parallel pool (parpool) using the 'bcmmjs' profile " and cannot go further.

Does that mean although the first instant only uses 10 workers, it still occupies 40 workers, which leads to the second instant cannot open the parallel pool?

And, in this case, the second instant will wait untill the first instant finished?

[Walter Roberson]

A pool can be created that gives multiple cores to each worker.

Is it using 10 workers each with 1 core, or is it using 10 workers each with 5 cores?

[Raymond Norris]

Before I provide a suggestion of what the issue could be, is bcmmjs an MJS profile or a profile for a 3rd party scheduler (e.g. PBS, Slurm)?