FAQ/Render nodes slow in loading comps

From VFXPedia

< FAQ
Revision as of 16:48, 14 February 2007 by Adrian (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

By default (if the FUSION_NETSENDCOMP env var doesn't exist on the Manager's machine or it's not set to "True") the Fusion Render Manager will read the comp itself and send it direct to the RenderSlave as part of the LoadComp command. The RenderSlave will dump that data into "Temp:" and load the comp from there. This is to get around issues where comps are being loaded from machine with a limited number of network connections (ie. non-server Windows). It does put more "load" on the Manager though.

If that env var is set to "False" then the RenderSlave will just be given the filename as part of the LoadComp command and it will load it normally (over the network) itself. So in that sense there could be quite a difference in the way comps are loaded using our RenderManager vs. a 3rd party one.

If there are still comp loading "lag" issues using the Fusion Render Manager with its default behaviour, then it's much less likely to be caused by network I/O.