NX9 - RAM Memory problem

[SvenVoeten]

Hi Everyone,

When I'm programming in NX after a while my pc is slowing down because NX is taking up all my RAM memory.
I'm not using large assembly's or extreme complex workpieces.
It seems that it doesn't matter what I open or how many files but how long NX is running.

My pc specs:
Intel Core I7-3610QM boost to 3.3Ghz
Nvidia GeForce GT 650M
8GB DDR3 RAM
750GB HDD

Greetings Sven

 

[vegetagaru]

it can be relative to graphics driver ?

NX8.5 User

 

[SvenVoeten]

I don't know, I've been working for 2 hours now on the same file on another computer and the RAM memory level isn't beet above 3Gb.
My computer has better hardware specs than the one I'm currently working.
I think its a setting on my computer that is wrong and that causes the level of the RAM memory to get to high.

 

[vegetagaru]

what setting you have on virtual memory ?

computer -> properties -> Performance -> advanced

NX8.5 User

 

[SvenVoeten]

8GB
I was also thinking in that direction. NX thinks I have 16GB RAM and allocates 8GB. I only have 8GB RAM in my computer so NX may only allocate 6GB or so.
Is there a way I can change how many NX can allocate?

 

[vegetagaru]

disable pagination file then reboot system and try it; may solve something but i think you should upgrade your mem size

NX8.5 User

 

[SvenVoeten]

Right now I'm working on a computer with only 4GB of RAM with no problems.
I'm doing more complex stuff than I was doing on my own pc when I had the problems so i don't think its the size of my RAM.

 

[vegetagaru]

try on disabling virtual mem.

NX8.5 User

 

[jhag84]

I too have had very high RAM usage climbing into the 12GB+ used by ugraf.exe

Intel i7 3770
16GB RAM
NX 9.0.3.4
Windows 7 Ultimate 64bit
GTX 550 Ti (latest drivers)

We just upgraded to NX9 at the beginning of this week and its happened a few times to the eight of us in the CAD room. I do run two sessions of NX sometimes, so I'll try to be mindful of checking the RAM usage and update this thread if I can find out more information why this is happening.

We also have NX 8 and 8.5 installed on our systems. Not sure if that has anything to do with it.

 

[vegetagaru]

i had on customers defaults "allways compress on save" on and removed it, it will run faster at least on saving. coz we compared the versions saved with crompressed and witouth compression and in a 4gb project it only saved like just 150/200mb


NX8.5 - NX9 User

 

[jhag84]

Today, Ive opened and drafted only four parts(one assembly, three regular parts) and already my UGRAF.exe is using over 3GB of RAM. I've noticed that while taking a view in drafting and simply moving it around, the memory used by UGRAF.exe raised fairly quickly.(more so in the assembly) Also, after closing a part, the memory did not clear.

I do not have "always compress on save" option on.

 

[jhag84]

I just deleted a part I imported at the wrong scale, to reimport it. While deleting the 120mb part, the Memory Used raised from 4GB to 6.1GB and after it deleted, did not lower.

 

[cowski]

If you are experiencing a memory leak, your best course of action would be to contact GTAC. They have the tools and know-how to dig into the technical details of your problem.

FWIW, I've been using NX 9 for a few months now and have not experienced a significant increase in memory usage.

www.nxjournaling.com

 

[Tingsryd]

FYI-
The other day I was crunching a rest mill operation using a small tool and the operation came after many other operations so it had a lot of calculations to do. I also had a z-level profile operation with a reference tool crunching at the same time. Ram usage was 14+ GB and after I closed the part file usage was still at 6GB; a little higher than a fresh reboot and not unexpected. IMO 16 GB is minimum for anyone who works with 3-D non-prismatic parts or large prismatic parts, where either type is going use 3-D IPW's, reference tools and parallel generating.



NX9
Migrate to 10 when 10.2 is released.

 

[SvenVoeten]

I've contacted GTAC and after some mails and testing, GTAC contacted nVidea because the problem was my nVidea Geforce 650M card.
Because a "gaming" card from nVidea isn't build for heavy graphics applications it's trying to compensate by using the processor and storing stuff in the ram memory.
nVidea wouldn't give any further support for the problem because the graphic card wasn't a certificated card. They only give support for the Quadro series.

Below, the last mail I received from GTAC that describes the advice they could give me.

"Sven,
as discussed on the phone, I've discussed this problem with a NX CAM colleague, he instantly asked for the graphics card in your system (nVidia GeForce GT 650M), beause of the influence CAM operations (tool path, simulation, visualization,...) have on the graphics card.
The nVidia GeForce GT 650M is a "gaming" card that doesn't have Open GL hardware like the certified Quadro graphics cards.
You can try to install newer drivers and/or configure this card for NX operations via Global/Program (Open GL) settings in the nVidia Control Panel.
Increasing the Windows swap file may also help."

I've got no complains to GTAC they really did there best to help me.
In the following next days I will check if the recommendations will work and if i get any positive effects I will post it here.

Greetings Sven.

 

[Tingsryd]

Well at least you know now you can restart once in a while to get your ram back. Technically GeForce cards support Open GL, yours should support Open GL 4.4, but the drivers for GeForce are much different from Quadros. I have dual GeForce 680's in a test computer and it is mostly used for crunching work units for the Stanford Medical School protein folding grid project as well as some MasterCam and NX testing and possibly *cough cough* just a bit of WoT.

On a side note...I can't speak for your 650M card (is that mobile?) but the other GeForce cards are actually the same hardware as Quardros; only the driver is different. A long time ago people used to flash high end GeForce cards into their Quadro counterpart because the GeForce cards are literally a fraction of the cost of Quadro cards even though the hardware was the same. Nvidia became a little trickier about it nowadays and although people cannot easily flash their cards, there are hardware straps on the cards which can be carefully altered so it makes it possible to turn a GeForce card into a Quadro and vice versa. The hardware straps are so the driver software knows which driver to install. I know people who made K5000 cards from their gaming cards for under $500. Of course there are ethical questions about doing this since altering a card could be considered altering intellectual property. Still an interesting topic IMO.

NX9
Migrate to 10 when 10.2 is released.