futureverse / futureverse/future

WISH: It should be possible to adjust the number of assigned cores

Open
#7 9 comments 0 reactions 0 assignees View on GitHub
enhancement feature request question
Dominant language
R
Stars
1k
Forks
92
PR merge metrics
No merged PRs in 30d

Description

_2016-11-03: Issue was originally on 'availableCores("mc.cores") should returngetOptions("mc.cores") + 1L' but it recently turned into a more general discussion on how to maximize core utilization. See below._

`future::availableCores("mc.cores")` should really return `getOptions("mc.cores") + 1L`, because from `help('options')`:

> `mc.cores`:
> a integer giving the maximum allowed number of _additional_ R processes allowed to be run in parallel to the current R process. Defaults to the setting of the environment variable `MC_CORES` if set. Most applications which use this assume a limit of 2 if it is unset.

Further clarification: Multicore processing is not supported, it would effectively correspond to `options(mc.cores = 0)` and in that case `availableCores()` returns 1.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.