Learning Forum

[Roberto]

Hello 

Will the opening of large assemblies or artboards be speeded up in future versions?
In the first versions of SpaceClaim 2017-2018 the opening of large assemblies with external components was faster, in the latest versions it is slow.
SpaceClaim takes a long time to search for the paths of individual external parts.
Isn't it possible to speed things up? Even opening detailed tables takes a lot of time

 

Best Regards

[Charudatta Bandgar]

Hello Roberto

It was supposed be faster with the current version, let me get more information if there is any change with regards to this.

Regards.

[Roberto]

Hello Charudatta Bandgar

Is just faster though there isn't much difference.
SpaceClaim especially struggles to load files that also have drawing format inside

Best Regards

[Charudatta Bandgar]

Hello Roberto

I am not aware of any change in the time it takes.  This could be highly variable depending on the user's PC.  Many factors could play a role.  I had discussion with the team, and these are some of the reasons that I could some up. 
This include things like:

• 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.

Regards.

[Roberto]

Hello Charudatta Bandgar

I'll answer all your points listed

1)The server disk is solid state and it's been a year since they bought it, by copying the files locally the loading times improve a little

 

2)The files are all on the server, and each contains a drawing

 

3)There are about 8500 components, more or less spaceclaim up to how many components works well at speed?

 

4)We have been reporting this problem for some time now, and I think it's a BUG.

As the convenient thing of SpaceClaim is to create the components inside the assemblies and then make them external, but in this way you create large files.

Will this problem ever be solved?
So this advantage of spaceclaim in creating parts inside assemblies is not very usable.
It would be great if when you externally convert a component it would purge all assembly information from the file information so that the file is small in size.
Or it would be nice if there was a batch file where it cleaned up all the information

 

Best Regards

[Roberto]

Hello Charudatta Bandgar Answer me by email in private, I have to ask you other things

[Charudatta Bandgar]

Yes Roberto

Lets continue the conversation over email.

Regards.

[Roberto]

Hello Charudatta Bandgar Do you have any news?

Regards