Q100489: Why Nuke creates multiple processes when launching

Follow

SUMMARY

With the release of Nuke 11, the Frame Server has replaced the Background Render when rendering image sequences. 

The Frame Server allows Nuke, Nuke Studio and Hiero to reduce render times by using multiple instances of Nuke to render with. This can be achieved via additional render processes launched on the local machine or external machines.

The amount of processes created is determined by the frame server processes option, within your Preferences window:

Depending on how many processes you have set to use, multiple Nuke processes will be spawned and appear in the OS process manager (e.g Task Manager on Windows, System Monitor on Linux or Activity Monitor on macOS).

NOTE: For rendering video files like .mov, the Background Render is still used.

When launching Nuke via the GUI or within Terminal mode, Nuke displays multiple processes within the Task Manager (Windows), System Monitor (Linux) or Activity Monitor (Mac):

 

NOTE: If you're looking to disable the frame server, please review this Knowledge Base article: Q100378: How to disable the Frame Server for Nuke, Nuke Studio and Hiero

 

FURTHER READING

For more information on Command Line operations, please refer to the following documentation link: Nuke Online Help - Command Line Operations

To learn more about rendering using the Frame Server, please refer to: Nuke Online Help - Rendering using the Frame Server

If you are seeing issues with custom Python scripts launching multiple times on launch, please refer to: Q100499: Custom scripts execute multiple times on launch

    We're sorry to hear that

    Please tell us why