This article explains two alternative methods that can be used to test the performance of Nuke nodes when trying to identify the cause of script slowdowns.
Performance Profiling mode
To run Nuke in Performance Profiling mode you need to use the -P flag when launching Nuke. A list of instruction on how to do this can be found below for each operating system.
Open a Command Prompt window and run the following command:
"C:\Program Files\Nuke14.0v5\Nuke14.0.exe" -P
Open a Terminal window from Applications > Utilities and run the following command:
Open a terminal and run the command:
Note: These instructions are based on having Nuke installed in the default location. If this is not the case then the commands will need to be modified accordingly to run from your custom installation location.
NOTE: On macOS and Windows, the CPU time is not currently accurate. On macOS, the CPU value is always similar to the wall time.
• wall - The time taken as it would be measured by a clock on the wall - the actual time you have to wait for the processing to complete. The wall time is also measured in microseconds.
• ops - The number of operators called in the node. Operators are Nuke's building blocks that perform certain tasks. Nodes can contain one or more ops.
• memory - The total amount of system memory used by the node.
Difference between methods
While the Profile node does provide quite a few new features such as charts and other GUI based diagnostics, it calculates performance based upon percent-based analytics rather than the timer-based analytics that the Performance Profile mode uses.
More information regarding both methods can be found respectively within either the Performance Profiling or Profile node documentation.
We're sorry to hear thatPlease tell us why