Q100072: Troubleshooting suggestions for when a Nuke script is unresponsive or slow



This article provides guidance on what to do if a Nuke script has become very heavy and slow to navigate.


If a script has become slow or unresponsive then we would recommend you do the following to either try and diagnose the causes of the slowness, or try to improve the current performance:

Test the script in safe mode
Testing the script in safe mode may help you identify whether the issue might be related to a customization/third party plug-in you're using, or Nuke itself. The following article provides instructions for how to launch Nuke in safe mode: Q100038: Launching Nuke/NukeX/NukeStudio in safe mode

Test with Script Profiling enabled 
This helps you see the total processing time spent on each node and identify a potential culprit. The processing time spent on each node is shown as: Red = slow nodes, Green = fast nodes
To launch Nuke with script profiling enabled you need to add the -P argument when launching from the terminal/command prompt:
Windows:   C:\Program Files\Nuke14.0v5\Nuke14.0.exe -P
macOS:       /Applications/Nuke14.0v5/Nuke14.0v5.app/Contents/MacOS/Nuke14.0 -P
Linux:          /usr/local/Nuke14.0v5/Nuke14.0 -P
Any nodes that appear red we would recommend you first try disabling to see if the script speeds up and then gradually enabling again with lower settings.
For more information, please reference Nuke's online documentation regarding script profiling.

Additionally, Nuke includes a Profile node to help measure performance in the script. More information on this node can be found in our online documentation for the Profile node.
As of Nuke 11.1v1, and later, we introduced the Profile node. This node allows users the ability to calculate the metrics of a node tree at the point the Profile node is placed.
When a Profile node is placed in the node graph and selected the Profile menu will open.

To run the profile, enter the selected frame range and data type then click, profile.
Once the data is collected, within the Profile menu the data will be generated and shown in a chart based upon percentage use.
NOTE: For more information on filtering this data, please refer to the Filtering Profile Data documentation
Disabling thumbnails or setting static frames
Disabling thumbnails, or setting them to static frames, may help reduce the amount of processing happening within the script. You can find more information about this in the following article:
Use Precomp nodes
By using the Precomp node you can save a subset of the node tree as a separate .nk script, render the output of this saved script, and read the rendered output back into the main comp as a single image input.
This speeds up render time, as Nuke only has to process the single image input instead of all the nodes that were used to create it. 
For more information, please reference our online documentation regarding the Precomp node.

    We're sorry to hear that

    Please tell us why