Set the swap to 25 gig and have the min/max the same so windows doesn't keep on dynamically resizing it. Also make sure your cache is explicitly set. Especially if you have floating profiles under windows then you run into the problem where lame windows puts tmp in a directory which lives on the server and or it gets copied back to the server every time the system logs out.
3rd, on your farm are you launching a render per core or are you multithreading? I would multithread if you don't have the ram since a frame per core uses far more ram. -deke On Tue, Apr 19, 2011 at 14:02, Francois Lord <[email protected]> wrote: > Are we the only ones to have problems closing Nuke after working on big > frames (4K) on Windows 7? It can take up to 20 minutes to close and during > that time, we can see the memory slowly being emptied in the task manager. > We didn't have that problem in Windows XP. We can kill the process and it > frees the memory instantly, but it's not a viable solution on the render > farm and currently we have frames that take 10 minutes to render when they > take only 1 minute in the UI. > Anything we can do about it, other then switching the farm to linux? > Thanks. > _______________________________________________ > Nuke-users mailing list > [email protected] > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > _______________________________________________ Nuke-users mailing list [email protected] http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
