Skip to contents

A batchtools backend that resolves futures sequentially in transient background R sessions

Source: R/batchtools_local.R
batchtools_local.Rd

The batchtools local backend is useful for verifying parts of your batchtools setup locally, before using a more advanced backend such as the job-scheduler backends.

Usage

batchtools_local(..., fs.latency = 0)

Arguments

fs.latency

[numeric(1)]
Expected maximum latency of the file system, in seconds. Set to a positive number for network file systems like NFS which enables more robust (but also more expensive) mechanisms to access files and directories. Usually safe to set to 0 to disable the heuristic, e.g. if you are working on a local file system.

...

Not used.

Details

Batchtools local futures use batchtools cluster functions created by batchtools::makeClusterFunctionsInteractive() with external = TRUE.

An alternative to the batchtools interactive backend is to use plan(future::cluster, workers = I(1)).

Examples

plan(batchtools_local)

message("Main process ID: ", Sys.getpid())
#> Main process ID: 620860

f <- future(Sys.getpid())
pid <- value(f)
message("Worker process ID: ", pid)
#> Worker process ID: 621503