Re: Detailing large assemblies

[Charudatta Bandgar]

Hello Evangelos Papageorgiou

The performance with subsequent releases of spaceclaim, the way it handles large assemblies has improved a lot. There are several things that decide how the SpaceClaim would behave with large assemblies. In large assemblies some times the external components could pose the lagging issue, because of additional information it has to store. Here is list of things that could be affecting how that is affected,

• Hard drive type, age/degradation, or level of fragmentation
• External file locations (e.g. local disk vs network location)
• Complexity of assembly (number and size of external components)
• Possible file inflation due to the continued use of external components.  This one could be substantial.  When an external component (let's name it EC) is saved within an assembly, location information for all other components from the assembly is saved within the external component and retained.  Each time EC is added to another assembly and saved, more assembly information is added to EC.  This can cause the file size to increase by orders of magnitude and will greatly affect performance.  This problem is not uncommon.  We now have a utility that will help remove this extra information.  The recommended workflow is to add the external component(s) and then use Source > Internalize All to create internal copies of the component and break the link to the original file.  Of course this poses the problem where updates to the master EC are not automatically applied to every assembly where EC is used, so it's not a perfect solution.  The work around would be to add the ECs last before the assembly is finalized.

For assemblies with components as much as 10000, this will still be little slow. Which version of SpaceClaim are you using? 2021R2 could be better at it too. Let me know if it answers you question.

 

It gets worse when working in views with "hidden line removed".

 Let me check, why this could be happening. Ideally there should not be this issue.

 

Is there a way to be as fast as putting dimensions in an AutoCad dwg file?

 Let me check with the team if there is any comparison with AutoCAD etc.

 

It could also be possible that the file while translating from the native format to SC, might have gotten corrupted, etc. Sometimes the constraints, relations (mirror, etc) could also cause slowing issues.

 

Regards.