Aside from generic recommendation in the the Release Notes: "For Windows 7, the minimum amount of memory is 4 GB, but we recommend 8 GB or 16 GB of memory as a starting point. Large models and assemblies or running multiple processes concurrently could boost the required memory for adequate performance." are there more specific memory requirements spelled out for NX11?
In other words, are there more concrete guidelines for determining a reliable memory configuration based on model size/complexity and/or feature use based on real world results?
Solved! Go to Solution.
The amount of memory required will depend on what you are doing. If you are doing machine design with assemblies of only a few hundred or thousand parts, then 4 Gb or 8 Gb would be sufficient. If you are doing machine design with many thousand parts, then you might need 16 or 32 Gb. If you are doing large complex FEA or CFD then you might need 32 Gb.
The best way to tell how much you need is to monitor your memory via Windows Task Manager. If you are using close to all of your memory, then you might need more. For example, on my system the "Physical Memory" is 32503 MB (32 Gb). But I am only using 6.22 Gb. If I ever see the amount of memory used getting close to 32 Gb then I would need more memory.
Can you speak to how to how I should or should not interpret the NX Memory Monitor versus the ugraf footprint I see in the task manager resource monitor? These shots are from the same session with an average-sized assembly open, but idle.
I always use Task Manager to monitor NX memory usage. You should add the "Working Set (Memory)" and "Commit Size" columns. The Commit Size tells you how much total memory NX needs. This is your best clue as to how much RAM your computer needs for NX. If the Commit Size grows much bigger than the Working Set then it indicates you are swapping to disk, which is bad. This will only occur when you start approaching the physical limit of RAM for the machine. In your case it appears that your machine has 32 Gb. Windows needs some of that memory, Outlook needs some, other applications need some, etc. If your ugraf.exe process ever grows to more than 24 Gb (assuming a 32 Gb system) then you will probably start to swap to disk.
In your case the ugraf.exe process is using slightly more than 1 Gb out of a total of 32 Gb. If this is an average size assembly, then you definitely have enough RAM. I would encourage you to open Task Manager and monitor the ugraf.exe process, and occasionally go to the Performance Tab to look at the "Memory" chart. After a couple of hours or days you will have a good feel for how much memory NX and other applications are using.
So I'm guessing this is why NX performance is particularly bad today (note when I first pulled it up the working set was 170,000 more or less):
Production: NX10.0.3.5 MP5 + patch/TC11.2
I'd rather be steemed than diseaseled
Those are both very small numbers: Working Set = 219 Mb; Commit Size = 644 Mb. If NX is slow then something else is the culprit.