Nuke - Managing Bigger Scripts

[brtnysprsfnclb]

Hi,
i am working on a big script at the moment (400+ nodes) and im at the limits of my machine.
Other scripts i worked on were very small (max. 100 nodes). Im looking for a tutorial or explanation
how to manage big scripts. Is there a way to prerender some parts of the script without reading in the prerendered
stuff manually?
I`m not sure about it but is it the right way to prerender some parts by a normal write node? Or is it a better way to seperate
all the parts in different 3D Scene nodes or something?

-Phil

[user_deleted]

400 nodes isn't really a big script so if you have a reasonably modern machine this should be totally ok.
you can use various Read/Write node combinations and set the render order knob in the write nodes to make sure images are rendered out before being used again downstream.
WriteA - render order 1
ReadA
comp away
WriteB - render order 2
ReadB
etc.

Always, check your bounding boxes to make sure they are optimized to avoid unnecessary render times and memory consumption.
Make sure your flipbook cache in the preferences is set to a fast local disk (cause it really is the entire disk cache, not just the flipbook location).

[brtnysprsfnclb]

Thx for your help. im working on an quadcore machine, 4 gigs ram. nuke says "keyer1: out of memory" and so on.
Ill check the cache and try to prerender some elemets.

Did nuke only use memory when the nodes are in use for the current viewer?

[fxnurbs]

I would say, there is a point where you r happy with your key, render it and input it insteed. Prerender what you can.
The roto and paint are the most memory consuming.

cheers