Problem summary
Rendering Nuke scripts that contain a Spherical Transform node, can take significantly longer to render on Linux machines compared to Windows machines that use the same specifications.
This issue appears to be related to memory allocation over threads, as the difference increases with the more threads that are being used.
The following results are from a test within Nuke 12.0v1 over 20 frames:
Windows 10: ~40 seconds
CentOS 7: ~4 minutes
This was reproduced on the following CPU:
Intel Xeon(R) CPU E5-2699 v3 @ 2.30GHz × 72
Reproduced by QA in Nuke-12.3.1main.606639, 150 frames:
Windows 10: 1 minute 15 seconds
CentOS 7: ~7 minutes
Customer reported version
Nuke 11.3v5
Customer reported platform
CentOS 7
Steps to reproduce
1) Open the attached script. It contains the following nodes:
2) Render the script.
3) Repeat these steps on both a Windows and Linux machine (using the same hardware)
Result: The takes significantly longer to render on Linux.
Expected behaviour
The time to render the script should be around the same on Windows and Linux
Actual behaviour
The script takes significantly longer to render on Linux.
Workaround
Limiting the thread count within Linux improves the rendering time substantially.
To do this, run the '-m' flag when starting Nuke:
/usr/local/Nuke12.0v1/Nuke12.0 -m 1
The above example reduced render times for 20 frames from ~4 minutes to ~20 seconds
Reproduced by support
This bug has been reproduced in:
Nuke 12.0v1 - Linux CentOS 7
Nuke 11.3v1 - Linux CentOS 7
Nuke 11.2v1 - Linux CentOS 7
Nuke 11.1v1 - Linux CentOS 7
Nuke 10.5v1 - Linux CentOS 7
Nuke 10.0v1 - Linux CentOS 7
*unable to test on macOS or CentOS 6 due to hardware limitations
Unable to reproduce bug in:
Nuke 12.0v1 - Windows 10
Earliest version tested
Nuke 10.0v1
- This issue appears to be in all versions of the product
