Start-up time Nuke via CGRU vs without CGRU
Posted: Wed Nov 09, 2022 10:18 am
Hi,
We are noticing a slow down in starting Nuke when we run it through CGRU versus starting Nuke from its regular path.
It usually takes 10 seconds or more extra when we run Nuke via the start_nuke script in the cgru folder.
When we run both from a command line with -V (verbose) mode on Nuke, the console stays silent for those 10 seconds before starting Nuke.
So, we are wondering what is actually going on during this time? Is CGRU first running additional scripts in the background or is there another explanation?
We are noticing a slow down in starting Nuke when we run it through CGRU versus starting Nuke from its regular path.
It usually takes 10 seconds or more extra when we run Nuke via the start_nuke script in the cgru folder.
When we run both from a command line with -V (verbose) mode on Nuke, the console stays silent for those 10 seconds before starting Nuke.
So, we are wondering what is actually going on during this time? Is CGRU first running additional scripts in the background or is there another explanation?