Memory Problems

[looslib]

We are trying to load a very large assembly in Wildfire. The workstation is
a dual 2.8Ghz IBM Z-pro with 3GB RAM.

When memory usage by Xtop approaches 1.35GB, Pro/E will suddenly disappear
and the designer loses everything. then it is 30-40 minutes to try and
reload the assembly.

We think one of the problems is that the design team uses a lot of copy-geom
features in their assemblies for references instead of map parts.
They also use heavy models instead of using shrink-wrapped assemblies.

Does anyone have any tricks for dealing with large assemblies in Wildfire?

We are contemplating a Unix box with 4-8GB of RAM. Problem with that is only
the one user would be able to load the entire machine. If we go this way,
what Unix works best with Wildfire? The last Unix box we had for UG was a
DEC Alpha running OSF/1.

Also, are there any problems with mixing Unix and Windows files in
Intralink?


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
CAD/CAM System Analyst
Ingersoll-Rand

 

[ProEpro]

Try making some simplified reps of the assembly. you could also load a graphics only simplied rep. At the open menu choose open rep.

talk to PTC you may need to tweak your windows enviroment settings.


ProEpro

http://www.whitelightdesign.com

Pro/E FAQ

http://www.whitelightdesign.com/servicestips.htm

 

[Hora]

Ben,

If you are running WIN XP, then go to System Properties->Advanced->Performances->Advanced->Virtual Memory->Modify...

Now you have several choises. Either to increase the virtual memory at double to your computer RAM or make it 0 (zero). I sugest you to try my second advice. In this way you will force WIN to use the whole RAM memory.

Is just a suggestion and I don't know if it will work in your case, but give it a try!

Good luck,

-Hora

 

[ProEpro]

One more comment: you do not have to have a Unix box to get more than 4 gigs of ram. The 64bit version of Windows XP can use at least 16 gigs. NTSI seems to be promoting it the hardest for Pro/E workstations.

ProEpro

http://www.whitelightdesign.com

Pro/E FAQ

http://www.whitelightdesign.com/servicestips.htm

 

[KimBellingrath]

You might want to look for files with a '.crc' suffix. These are circular references caused by assembly reference mistakes. They kill productivity by causing the process to run in circles for many cycles before moving on. You will see this type of message if you look at a text of the crc file: LOOP # 1

Depth of loop is 3

Feature number 9 (COMPONENT, id = 70)
in model 85540763 refers to:

Feature number 5 (SURFACE, id = 263)
in model 85540763M4 refers to:

Feature number 9 (COMPONENT, id = 70)
in model 85540763 - circle closed.

When the system encounters this point, it doesn't know which feature to establish first and runs in circles trying.
Hope this helps,
Kim