This is not directly related to your problem and I don't know the size
of you're studio but, about "overloaded network":
Write images from nuke directly on a network folder decrease drastically
the whole network performance, specially if there is many users who do that.
I consider to save image file on local first and move it to his
destination folder (in the network) next.
I know this doesn't help you with you diskcache problem. :(
On 05/09/2012 12:08 PM, chrissowa wrote:
I am fighting with the diskcache node too ...
our networktraffic is often pretty overloaded and therefore we tested
this node straight behind the readnode (source) with the "precache"
function.
The funny thing is, after rendering the playback is like:
* first 1/3 is very slow, seems to read from diskcache now
* last 2/3 are fast and seems to be in ram?
the first 1/3 is even slower than loading over network ...
the only clue i have about that is because of disk speed that is maybe
too slow for reading the 32bit cache?
its a common disk and the nuke disk cache is about 200gb big. this
should be enough for about 1000 frames of 10bit dpx.
So i need to build a proxy workaround or?
a statement by the foundry about this node would be really great.
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
