A cluster object created by makeCluster, or an integer to indicate number of child-processes (integer values are ignored on Windows) for parallel evaluations (see Details on performance).
I'll put in a little work around, but we should probably figure out how to allow a person to pass in their own cluster object rather than using an integer number of workers.
There is a bit of overhead to spin up a cluster and shut it down. With future, the cluster gets created a-priori, which is akin to dask or the cluster from parallel. I think it's probably going to be best to accept that kind of cluster input in some way in addition to this simple setting of the level of parallelism on a per call basis.
Describe the bug From pbapply docs:
I'll put in a little work around, but we should probably figure out how to allow a person to pass in their own cluster object rather than using an integer number of workers.
There is a bit of overhead to spin up a cluster and shut it down. With future, the cluster gets created a-priori, which is akin to dask or the cluster from parallel. I think it's probably going to be best to accept that kind of cluster input in some way in addition to this simple setting of the level of parallelism on a per call basis.