This article describes the recommended way of testing your Frame Server setup to ensure it is using your network slaves and not the local processes.
More information on troubleshooting different issues can be found under Q100080: Troubleshooting Nuke Studio Frame Server issues
1) Disable the local Frame Server processes to confirm that your setup is exclusively using network slaves.
For this please change the following setting in NukeStudio on your master machine:
Edit > Preferences > Threads/Processes > frame server processes to run
This setting specifies the amount of Frame Server processes on your local machine, the default value is 6.
To stop using any local Frame Server processes set the value to 0.
NOTE: For the setting to be applied and used correctly please restart NukeStudio before moving to step 2.
2) Check if any network slaves are connected to your master machine and are working correctly.
Open NukeStudio after having followed step 1 and run the following lines in the Script Editor:
from hiero.ui.nuke_bridge.nukestudio import frameServer
print [worker.address for worker in frameServer.getStatus(1).workerStatus]
Any process shown should be a slave process (the local Frame Server processes have been deactivated in step 1)
3) Render a comp sequence to test if rendering using the Frame Server is working correctly.
4) To use your master machine in addition to the network slaves Frame Server rendering, change back the NukeStudio 'frame server processes to run' value from step 1, to non 0.
Keywords: Frame Server, testing, setup