|10 October 2013||#1|
Nuke is not using all resources in the render farm
I have Nuke and 10 licenses to render in the farm.
I'm using just one node with 32 threads and 64 gigs.
The rest is for Arnold. Comparing the resources used
in both of them. With one super heavy loaded nuke script;
with all the expensive nodes. And a decent Arnold scene.
Both using one different node with the same configuration.
The discrepancy is a huge, around Arnold 90% and nuke 10%
I will appreciate any help you can give me.
|11 November 2013||#2|
VR Pipeline Supervisor
Los Angeles, USA
There can be one of two problems. First Nuke can often be i/o bound, for example Nuke is waiting for files to copy to the cache before it can process them. You can speed this up by making sure most of you files are in a scanline file format like EXR zip 1 scanlines. Often images are a tile based image format which severly slows down processing in Nuke so it has to internally convert it to scanline in the cache before it can process it. EXR out of most software renderers are tiled, also tiff files are very slow in Nuke.
Secondly not off of Nuke's nodes are fully threaded. So typically I suggest to submit a render per 2-4 cores instead of 1 render for all cores.
|Thread Closed share thread|