Hardware Suggestions for very large assemblies

Hardware Suggestions for very large assemblies

Olgan
Enthusiast Enthusiast
1,742 Views
7 Replies
Message 1 of 8

Hardware Suggestions for very large assemblies

Olgan
Enthusiast
Enthusiast

Hi everyone,

 

There is a page with minimum and recommended specs for Inventor 2024 but it lists large assemblies as more than 1000 parts. (https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/System-requirement...)

 

Can someone suggest me hardware specs for assemblies with 5000 parts (about 200k occurrences)?

 

We have performance problems with our computers. I'm guessing it has more to do with company firewalls and such but want to be sure before pursuing those uncharted waters

 

Thanks

0 Likes
1,743 Views
7 Replies
Replies (7)
Message 2 of 8

JDMather
Consultant
Consultant

@Olgan 

Before looking at hardware solutions - I would first make sure best practices are followed for Inventor modeling techniques.

Almost invariably when I examine behavior that you describe I find less than ideal modeling practices.

1. Unconstrainted sketches.

2. Pattern of sketch elements rather than component, body, feature patterns.

3. Other unnecessary duplication (mirror, dimensions and other...)

4. Poor assembly constraint strategies.


-----------------------------------------------------------------------------------------
Autodesk Inventor 2019 Certified Professional
Autodesk AutoCAD 2013 Certified Professional
Certified SolidWorks Professional


Message 3 of 8

Olgan
Enthusiast
Enthusiast

hi JDMather,

 

Believe me we've been there. We even had redundant constraints in the beginning. 

 

We don't have the issues you've listed. All our sketches are fully defined. We never pattern sketch elements. We use mirror only when deriving from a base part which we name with _L suffix base being the one with _R. Our subassemblies have defined centerline and elevation planes which are used to connect with master assemblies origin planes. No pattern element is used in constraints, etc

0 Likes
Message 4 of 8

Mario.VanWiechen
Advocate
Advocate

Most effective method I found was to use " Defer Update " 

Turn that on with a plan to make multiple changes, takes planning and a very clear idea of what you want to do.

When the planned changes are done click the update icon and wait for it to happen. Grin 

 

 

MarioVanWiechen_0-1710248856868.png

 

Message 5 of 8

JDMather
Consultant
Consultant

Next step...

InvMark by TFI & Cadac, Inventor Performance Hardware Benchmark Tool with Leaderboard - Autodesk Com...


-----------------------------------------------------------------------------------------
Autodesk Inventor 2019 Certified Professional
Autodesk AutoCAD 2013 Certified Professional
Certified SolidWorks Professional


Message 6 of 8

Anonymous
Not applicable

Oh boy do I know your pain.

 

I was tasked with this very issue about 6 yrs ago. There's a number of things I needed to address and you may very well be in the same boat. Files that would take 3 hours to activate were brought down to under a minute.

As JD points out, bad practices can and will cause numerous issues. Blown constraints were a huge matter.

But you seem to be on the right path.

Some of the items I had to address:

 

Of course, as you stated, keep the files as clean as possible. Even run them through the Inventor task scheduler as I show here: Inventor 101 – Knock Knock Knock, “Housekeeping!” — Celtic Design Services (cdscad.com)

This process works wonders in my experience.

 

Use of low detailed Model States (or Level of Detail if you're on an older release), set Express mode accordingly. I think this defaults to 500 parts. (we'd have tens of thousands of parts and a good portion were unique instances). Be sure your temp files are cleared and clear it often.

 

We used Factory Design and our assets were highly detailed when they didn't need to be. I'd suggest maybe doing something along the same lines but with simplified components in the upper level assemblies. A lot will depend on your internal processes as well.

 

Another big memory hog is any reflectivity on your materials (same for textures). Refrain from using any textures and reflectivity type materials.

 

If and when it still comes down to hardware, make sure your CPUs are of the latest generation. Even with new Dell workstations, we found the bottleneck was the CPUs, as soon as we replaced them with the latest gen, we saw a marked improvement over what we had already done.

 

Once the users were aware of these items and what to look out for/correct, our files opened within minutes. We're talking 5 miles of conveyors under roof, they were huge.

 

Hope what little info I offered helps. If I recall other items we needed to address I'll post here.

Message 7 of 8

Olgan
Enthusiast
Enthusiast

@JDMather Thank you, I'll be back with the results. 

 

@Anonymous The information you shared with the link; it was not what I was looking for but it was what I needed. So thank you very much for that.  We already used level of detail but with model states we need to be extra careful because now its like having different assemblies in same .iam.

 

We don't use material properties much, using steel-mild for base. Only texture we have is for walkway gratings I think.

 

Can I ask for your hardware specs, since your scope of work seems similar?

0 Likes
Message 8 of 8

Olgan
Enthusiast
Enthusiast

hello again,

 

I couldn't upload the benchmark results because of the company firewall i guess. Anyway, took a screenshot, hopefully it helps.

0 Likes