Skip to main content

Execution caching

Given our reproducibility guarantees, jobs are cache-able unless otherwise specified.

When a job is cached, its output is directly generated from a past equivalent execution without consuming any computational credits.

This feature is relevant when implementing complex client-side workflows. In such cases it's common finding that different steps (BatchX jobs) of the workflow are equivalent to others from previous executions. This feature makes the workflow skip those steps, saving money and time.

Two BatchX jobs are considered equivalent when:

  • Their image coordinates match.
  • Their input parameters are equivalent:
    • For non file parameters: Their values are equal.
    • For file parameters: Their values correspond to aliases of the same file (pointers to the same data).
info

Notice that run-time parameters like vCPUs, memory or GPUs are ignored for caching purposes (see reproduciblity conditions).

Running a job with caching disabled using the CLI:

  1. Follow the steps at Submitting a job, passing the -n (--nocache) parameter.

****