Skip to main content

Nuke - Rendering on the farm

Submitting your comp to our render farm is quite easy. First you need to make sure that all the files used in your comp (and your Nuke file itselfitself, of course) are stored on our Storage server. After that justThen select the writeWrite node you want to render and click theRender "> Submit to Deadline"Deadline in the menu bar, or press F5. The render on farm button that'son undera ShotGrid write node opens the Rendersame menuwindow.

bar

[Screenshot item1: (Submit to Deadline window, More options closed]

Most of the time you only have to check the name, the frame range and the mode, and press OK.

Job

  • Submission name: the name of your job in the Deadline Monitor. Filled in with your script name.
  • Comment: shown in the Comment column of the Monitor. Optional.
  • Department: just a label, you can alsoleave pressit F5):

    on

    Nuke15.0_1F8CKPu2vs.png

    2D.
  • You

will be greeted with the following menu:

Nuke15.0_TT5aJySCPz.png

A couple things to note:

Render

  • ThePriority: jobs with a higher priority optionare determinespicked howup manyfirst machineswhen willa bePC ableis tofree. runLeave your render. You should leave thisit at 70 unless you've agreed on a different number with your class' render managers.managers.
  • TheSubmit optionssuspended: the job waits in the queue until you resume it in the Monitor.
  • Frame range: lightglobal, uses your project frame range, mediuminput, heavy,the frame range of the Write node, and extremein-out determinethe in and out points of your viewer. You can also just type a range.
  • Mode: how much a single PC on the farm should render at once. If you have a fast comp, one PC willrenders be able to render 4 frames simultaneously without a problem. If you have a slow comp and useat the extremesame option,time one(see PC will render 1 frame at a time. So, a light render is theoretically 4 times faster than an extreme render. However, you will cause PCs to hang and crash when you submit an especially slow comp using the light option, so try to judge which option suits your comp best.below).
  • TheEnable smart frame spreadingspreading: checkbox causes your frames on the farm to be rendered in a different order. Firstrenders the first frame will be rendered,first, then the last frame,last, then the middlemiddle, frame,and afterthen whichfills in the blanks will be filled ingaps evenly. ThisHandy is useful if you're submitting a comp that takesfor a long time to render andwhen you want to know quickly seewhether ifit it's rendering successfullyrenders all the way through.

Modes

One PC on the farm can render several tasks of your job at the same time. The mode decides how many:

  • light: 10 tasks at once on a PC, 3 frames per task
  • medium: 5 tasks at once, 2 frames per task
  • heavy: 1 task at a time, 1 frame per task
  • custom: type your own numbers

A light render is a lot faster, but a heavy comp in light mode makes PCs run out of memory and crash. That's why the submitter suggests a mode: it looks at the nodes that feed your Write (how many there are, and whether there are 3D renders, deep or retimes) and picks that mode for you. Next to the mode you can see why, for example suggested ยท 3D render, deep. Nothing is rendered for this, so it's a guess; you can always pick another mode.

Do your renders still crash with memory errors? Choose a heavier mode. The farm also does this by itself after a few crashes, see ErrorTriage.

Rendering a movie (.mov, .mp4, ...)? A movie can't be split over several PCs, so the whole range renders as one task on one PC, and the mode is hidden. This is much slower than rendering an image sequence: for long or heavy renders, render EXRs and make the movie afterwards.

Farm

  • Pool: only PCs in this pool render your job. Leave it on none unless you've agreed otherwise with your render managers. For example, 128gb only renders on the PCs with 128 GB memory, for very heavy comps.
  • Secondary pool: PCs in this pool pick up your job when the PCs of the first pool are busy.
  • Group: leave this on none.

More options

Click More options for the settings you'll rarely need.

[Screenshot 2: Submit to Deadline window, More options open]

  • Use GPU: lets GPU nodes (ZDefocus, Kronos, BlinkScript, Inference, ...) use the graphics card instead of the processor. On by default. Turn it off when a GPU-heavy script crashes on the farm: all tasks on a PC share one graphics card.
  • Machine limit: the most PCs that render your job at the same time. 0 = no limit.
  • Machine list: only these PCs render your job, or with Machine list is a deny list on: these PCs never render it. Use Pick... to choose them from a list.
  • Wait for jobs: your job only starts when these jobs have finished, for example the Houdini render you're comping. Use Pick... to choose from your jobs.
  • Task timeout (min): a task that renders longer than this is stopped and tried again. 0 = no limit.
  • On job complete: Archive or Delete removes the job from the Monitor when it's done. Your rendered files are not touched.

Checks before submitting

When you press OK, the submitter checks your script for the most common reasons a render fails on the farm:

  • Your script has to be saved on the storage or education server. If it has unsaved changes, it asks to save it.
  • Read nodes or a Write node with a local path (like C:\ or your desktop), and Read nodes with errors: you get a warning and can still choose to submit.
  • Proxy mode on without a proxy path on the Write: it offers to turn proxy mode off.
  • MagicDefocus is not supported on the farm: replace it with OpenDefocus. Disabled MagicDefocus nodes are fine.
  • NeatVideo nodes: we only have a limited number of licenses, so your job gets a license limit. See LicenseLimiter.
  • Frames that already exist in your output folder: it tells you which ones, so you don't overwrite a render by accident.

After submitting, your job shows up in the Deadline Monitor. If something goes wrong during the render, check the job comment first; our event plugins explain there what happened.

Deadline submission tools developed by Gilles Vink.Vink, updated by Robbert Scholten