Create a ticket

Q100072: 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
This helps you see if the issue might be related to a customization/third party plug-in you're using or Nuke itself.  More information: 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/ -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.
Disabling thumbnails or setting static frames
This will help reduce the amount of processing happening within the script.

More information: Q100036: Improve script performance by disabling thumbnails or setting them to static frames in Nuke

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.

Nuke, NukeX, unresponsive, slow, hang, hanging, safe mode, script profiling, precomp, thumbnails, static frames

Was this article helpful?

We're sorry to hear that

Please tell us why
1 out of 6 found this helpful


  • Avatar
    cool1986vfx cool1986vfx

    Btw, If Foundry make one small fix I`ll use Precomp node next time, for Fix Precomp node and make it faster its just need keep same tree inside Precomp but put Read node with same Write path for Output. Its not make a sense Precomp node read for example 500 nodes instead just one Read node on the End 

    All The Best

    Evgeny S.