Hi Peter
I did try the simple defocus tip - but it doesn't use all the cores at 100%
i get half of the cores being used ( 8 threads out of 16) - and out of
that half - only one of the threads is using a full 100% - the rest are
down at around 10% usage
This sound right?
Neil Scholes
www.uvfilms.co.uk
+44 (0) 7977 456 197
On 06/12/12 11:57, Peter Pearson wrote:
On 06/12/12 11:45, Neil Scholes wrote:
Hi Colin -
thanks for the tip - i just tried - it does give the same results
Nuke does read my 16 threads - even at start up
It seems this is how Nuke handles things...
Some nodes are single-threaded only, so not everything can be
multi-threaded, but a fair amount of stuff should (disk IO allowing)
run across as many cores as you tell Nuke to, at least on Linux (Nuke
on Windows has a few more issues in this area that the Nuke team are
currently looking into).
Did you try my suggestion of the defocus node as a simple script, just
to check that Nuke's config is okay to allow it to use all the threads?
If that does work (use all your cores fully), then it's either disk IO
contention (the disk trying to read and write at the same time) or a
certain Nuke node in your tree that's preventing it. Some 3D nodes
(DisplaceGeo especially) are single threaded-only for some things.
Peter
_______________________________________________
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
