Skip to main content
voyager cloud farm renders a frame range on several machines at once. It leases them from a snapshot, hands each the next chunk of frames from one shared queue, checks the outputs, pulls them back and releases every machine it leased when it ends, even when it fails or you press Ctrl-C.
Before you start: the voyager CLI (quickstart) and a snapshot of a machine that has your scene on it. Each farm machine bills by the second like any other; your plan sets how many you can run at once.

Set up once, then farm

1

Put the scene on one machine and snapshot it

Set up one machine with everything the render needs, then save its disk. Here, the scene from Render with Blender:
save keeps the machine’s disk under the name farm-scene (saving the name again moves it to the new state). Release the setup machine: the farm leases its own.
2

Farm the frames

The command after -- runs once per chunk, with {start} and {end} filled in. --expect names one file per frame, and every one must exist before the chunk counts as done. The frames land in film/shot/out/. This run took about a minute and a half, leasing included, and the farm released its machine at the end.
Raise --machines to split a long range: each machine takes the next chunk as it finishes, so a slow machine never holds up the rest.

Options

A failed chunk is retried on another machine, three tries in all. A machine that fails two chunks, or dies, is released and replaced.

A budget for the whole farm

  • At --budget: once what the farm has spent, plus one more chunk, would pass it, no new chunk starts. Running chunks finish and are pulled, and idle machines are released. The report lists what is done and what is left. Run the farm again with --resume and a higher --budget to finish.
  • At --ceiling: every farm machine is paused, with its disk kept. farm cleanup releases them.
  • Replacements: a machine that replaces a failed one gets only what is left of the ceiling, never a fresh share. A machine that went away counts at its full cap until Voyager confirms what it cost.
  • If the CLI stops: each machine carries its share of the budget and ceiling, so Voyager pauses it even with nobody watching.
The same works for task farms (--tasks).

Encode on the machine

Pull one video per chunk instead of thousands of frames: encode on the machine and pull only the video.

Farm a list of tasks

Not every job is a frame range. --tasks farms any list of independent tasks, such as shots, seeds or scenes: one per line of a file, with the same queue, retries, checks, pulls and release as frames.
shots.txt
  • Tasks are numbered 1 to N in file order. In the command after --, {task} is the task’s line as written and {index} is its number. Without a command after --, each line is itself the shell command.
  • Name outputs in --expect and --pull with {index}, never {task}: a line can hold spaces.
  • Each task’s whole log comes back as <--out>/logs/<n>.log (without --out, beside the farm’s record in .voyager-farm/).
  • --json lists every task with its status, tries, machine, log and outputs, plus the credits the farm spent.
  • A file takes up to 2,000 tasks. --chunk is for frames only: each task is its own chunk.
A three-task farm on one machine took under a minute, leasing included, and released its machine at the end.

Run something when the farm ends

--on-finish 'cmd' runs a command on your own computer once the farm ends, whether it is done, failed, stopped by Ctrl-C or left a machine it couldn’t release. The command gets the farm’s summary as JSON on stdin, and VOYAGER_FARM_STATUS (done, failed, stopped or unreleased), VOYAGER_FARM_NAME and VOYAGER_FARM_RECORD in its environment. Its output goes to stderr, so --json on stdout stays clean, and its exit code never changes the farm’s.

If the farm stops

The farm keeps a record in .voyager-farm/<name>.json (--name sets the name).
  • Continue: voyager cloud farm --resume .voyager-farm/<name>.json skips the chunks that are done and reuses machines still up.
  • Clean up: voyager cloud farm cleanup <name> releases every machine a crashed farm left. Every farm machine carries the farm’s tag, so even a machine whose lease answer was lost is found.

Next

Concepts

What snapshots keep, and what each machine state bills.

Render with Vork

Vork splits a long render over the GPUs of one machine by itself.