Hey all - I've been rendering a big sequence through nuke, and i've noticed that on our dual quad-core xeon mac workstations, nuke never uses more than 800% of the cpu (out of a total of 1600%, each 200% being a hyperthreaded core).
I know that compositing is much heavier on memory and disk access than 3d, so I don't expect to see the sustained 1600% I get from my 3D renders. However, even with that limitation I'd expect to see some places where the information is already in memory and nuke can crank out some calculations with everything I've got. Has anyone else noticed this limitation? -Mike
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
