Time-shift for greener, cheaper runs

Some work doesn’t need to start now — it needs to finish by some time. If you tell Komputo a deadline, it can wait for the greenest (or cheapest) window before that deadline instead of running immediately on a dirtier, busier grid.

When to use it

Time-shifting fits batch work with slack: nightly training runs, weekly reports, re-indexing, large evals. It does not apply to anything serving live traffic — a request can’t wait for cleaner electricity.

Mark the job deferrable

Add a relative deadline and make the job interruptible. The deadline is +<n><unit>, where the unit is minutes, hours, or days.

name: nightly-eval
image: registry.komputo.eu/examples/eval:latest
command: python eval.py
resources:
  accelerators: H100:8
policy:
  optimize: greenest-eu
  interruptible: true
  deadline: +12h

With optimize: greenest-eu, Komputo searches the carbon forecast for every eligible EU region and picks the window with the lowest expected grid intensity that still finishes by the deadline. Use optimize: cheapest-eu to shift toward the cheapest window instead.

See the chosen window before committing

Preview the placement to see when the job would start and what it saves:

komputo run nightly-eval.komputo.yaml --preview

The preview reports the recommended start time, the region, and the CO2 avoided versus running right now. Drop --preview to submit; the job sits in a held state until its window opens, then runs like any other.

What you get back

The receipt records the window the job actually ran in, the grid intensity at that time, and the resulting CO2 — so the saving is auditable, not just promised.