Increasing Performance in Nuke 6.2v1

[snowman25]

I'm having a problem with Nuke 6.2v1 where it is freezing up my Windows machine for a few minutes, and wanted to know if there is anything that can solve this

I have a Dell Precision T5500 workstation with 12-core Xeon processor and 24 GB RAM running Windows XP x64 SP2. I set the total paging file size to 24GB

The problem happens when Nuke is doing an operation and taking 23 MB of memory according to Windows Task Mgr, but I see the Virtual Memory size of the NUke 6.2 process to be 8 GB

Thanks

[Gentle Fury]

Have you tried updating to the latest version? They release fixes in each point release.

[snowman25]

Unfortunately, I cannot upgrade to the latest version of Nuke 6.2v2. there are different dependencies relating to Nuke 6.2v1 that prevent me from going to the latest version

[Gentle Fury]

what dependancies have you built into 6.2v1?

I've never had that issue...gizmos are universal....

[theLifeguard]

Have you tried changing your Auto save preferences? I found mine was getting hung up because it was force auto-saving too often. I increased the time, and it stopped hanging up as much, just make sure you save more often or you'll be more likely to lose more work if you crash...

[snowman25]

Yes, I have changed the Auto-Save settings in Nuke 6.2v1 to every 600 seconds, instead of every 30 seconds. I'll have to test this to see if this change will make any difference.

I also changed to a more powerful workstation since this last post. I know have a machine with 24 Xeon 2.4Ghz processors and 48 GB RAM. I did increase the size of the paging file to the max 48 GB. I'm hoping this will also help the problem.

I did notice that Nuke was taking a whopping 3 GB of memory in Windows Task Manager.

[snowman25]

I also examined some other settings within Nuke and was wondering if altering any of these would increase the performance of Nuke and keep it from freezing up:

Cache Memory Usage = 80%
Disk Cache = C:\Temp
Disk Cache Size = 50 GB
Paint Disk Cache Size = 50 GB
Nuke Memory Available for Paint = 75%

Of course, the best solution for Nuke would probably to run it on Linux

[Andreas.Jablonka]

yeah its not the workstation man, i find cache to 50% is often best at it does not start to swap/page unless your really hitting a big comp. maybe defrag you c drive. its the same that windows is running on, you could move that to a faster drive and a partition that is non windows os.
linux would be best yes.

[snowman25]

Yeah, I opened a ticket with The Foundry and they also suggested to upgrade to the latest version 6.2v4 -- I also submitted a copy of the Nuke script that I was running when the Windows machine jammed up -- and The Foundry was able to run it fine under 6.2v4

Another suggestion I received from another discussion group was to look at the GPU driver, since there are some known issues with the cuda cores and OpenGL. In this particular instance, I have a nVIDIA Quadro 6000 GPU - with 6 GB on-board RAM and driver version 267.17

[djati waskito]

Hi Snowman,
I had the same prob, almost like you. but since i move to Windows 7 x64 Ultimate , I dont have any problem in Nuke, even I have not a good specs Workstation like you, I designed my own specs. INTEL i7 3.0Ghz|NVIDIA 9600GT 1GB|14RAM|. I hope this helps.

goodluck

Kit
www.vimeo.com/kitovfx

[beaker]

also under windows it helps to move your autosave location locally.