ID 362953 - Running Python through the Script Editor within Nuke 11 releases appear to be significantly slower that Nuke 10.5 releases.

Follow

Problem summary
Running Python through the Script Editor within Nuke 11 releases appear to be significantly slower that Nuke 10.5 releases.

This issue only appears to occur on Linux-based distributions and only in Nuke 11 releases.

Customer reported version
nuke.11.2v3

Customer reported platform
centos7

Steps to reproduce

1) Open a new Nuke session within a Nuke 11 release on a Linux machine

2) Open up the Script Editor and paste the following callback test snippet into the window

def test():    return ""import timefor t in range(0, 10):    start_time = time.time()    for i in range(0, 1000000):        b = test()    print time.time() - start_time

3) Repeat the above process using a Nuke 10.5 release

4) Compare results between both release versions

Result: Results can vary over distributions, but there will be a significant difference between the Nuke 10.5 and 11 releases.
In the below example the difference is an average of 0.1457 seconds in Nuke 10.5v7 to 0.2592 seconds in Nuke 11.2v3





Workaround
Unknown.

Reproduced by support
This bug has been reproduced in:
Nuke 11.2v3 - CentOS 6.9
Nuke 11.2v1 - CentOS 6.9
Nuke 11.1v5 - CentOS 6.9
Nuke 11.1v1 - CentOS 6.9
Nuke 11.0v4 - CentOS 6.9
Nuke 11.0v1 - CentOS 6.9 - regression

Unable to reproduce bug in:
Nuke 10.5v7 - CentOS 6.9 - Windows 7 - MacOS 10.13.6

Earliest version tested
Nuke 10.5v7
- This issue no longer appears in this version and has regressed

Expected behaviour
There should be no difference between the python callback speed in Nuke 10.5 to Nuke 11 in Linux distributions

Actual behaviour
There is a significant difference between the python callback speed in Nuke 10.5 to Nuke 11 in Linux distributions
 

    We're sorry to hear that

    Please tell us why