×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Memory Problems

Memory Problems

Memory Problems

(OP)
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

RE: Memory Problems

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

RE: Memory Problems

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

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources