Create a ticket
Follow

Q100072: Nuke script is unresponsive or slow

 

SUMMARY

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

MORE INFORMATION

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:
 
 
TROUBLESHOOTING

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 instruuctions 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\Nuke12.2v2\Nuke12.2.exe -P
OSX:              /Applications/Nuke12.2v2/Nuke12.2v2.app/Contents/MacOS/Nuke12.2 -P
Linux:           /usr/local/Nuke12.2v2/Nuke12.2 -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 our 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.
 
IMPROVING PERFORMANCE
 
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.
Was this article helpful?

We're sorry to hear that

Please tell us why
1 out of 1 found this helpful