Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Model "bloat"
daniel_cook
Member Posts: 48 PRO
in General
Not sure if this has been discussed before (couldn't find any specific mentions).
When you have a large model - i.e. an assembly with a 1500+ unique parts and several thousand instances, then you start cutting details out (like a client wants to remove a section of the processing line, etc) - i.e. actual deletions, not suppression - how does Onshape handle this? Does it reference that all this detail still exists then deletes it before it renders on screen - as in does it load the model / assembly sequentially in the order it was built? or is it smarter than that?
I just notice that my models tend to get "bloated" and deletions sometimes make it worse. But that might just be my feeling (and blood pressure boiling when clients ask for sweeping changes when the model is already getting laggy from size.
When you have a large model - i.e. an assembly with a 1500+ unique parts and several thousand instances, then you start cutting details out (like a client wants to remove a section of the processing line, etc) - i.e. actual deletions, not suppression - how does Onshape handle this? Does it reference that all this detail still exists then deletes it before it renders on screen - as in does it load the model / assembly sequentially in the order it was built? or is it smarter than that?
I just notice that my models tend to get "bloated" and deletions sometimes make it worse. But that might just be my feeling (and blood pressure boiling when clients ask for sweeping changes when the model is already getting laggy from size.
0
Comments
The performance should be very good in this document. The reason is the structure in how it was built. Note how all the assemblies and subassemblies are not in one document. They are linked in.