BEST PRATICE CONCERNING CONFIGURATIONS

rick_randall

Awhile back I had to create my own library of AN/MS hardware and might not have set it up very efficiently . I ended up with a single, (simple part, a hex head bolt in this case), that has literally hundreds of configs. - question is, do I take a performance hit in large assemblies when using many instances of this bolt?  Should I set up my library with more parts (with smaller number of configs.)?   Recommendations?

Does Onshape have to grind though all the variations of the configs.(for each instance) - or does it just take a snapshot of the one configuration, and use that one simple case, when loading?

    This model shows the usage - but takes 1 or 2 mins. to load (only external components are shown)

https://cad.onshape.com/documents/df157a1cba8969b417b1bc0e/w/1c77d234890bfe7f6c31be4e/e/227a6c7eedf93af21a8d32c9

In my case I can live with the load times, but I'm just wondering if cleaning up my configured files in my library  will gain any real appreciable change in regen / load times - or am I chasing my tail? 

NeilCooke

If you use the different configs of the same part in an assembly, Onshape will regenerate the entire Part Studio for each config it uses. Versions will improve this, but removing the helical threads will make it much faster!!!

eric_pesty

It opened up in about 20s for me...
However I noticed you have the bolt in the same workspace, this will slow you down...
Move you bolt to a different document so that a version is referenced and it should speed things up, at least in theory

rick_randall

Thanks Eric, I'll look into that. 

And I guess I had some updates that give me the long load time - It's as you said now, about 20 sec.

NeilCooke

If you use the different configs of the same part in an assembly, Onshape will regenerate the entire Part Studio for each config it uses. Versions will improve this, but removing the helical threads will make it much faster!!!

rick_randall

Neil, thanks for the clarification. I may want to revisit some parts in my library, and break them down into smaller chunks. When I make 3d threads I use versioned configured parts that I named taps and dies, then deriving them into the bolt part, and then do a boolean subtract (instead of modeling the thread in the each bolt part). This seems to make the threaded bolt regen quicker, but maybe it's just my imagination.

  I understand that even one or two 3d modeled threads become a nightmare in drawings, but the purpose is to create detailed pictures for a build manual (not 2d production drawings), and it is important to show assemblies in a realistic appearance. Having said that, Onshape does a fantastic job of handling 3d threads as long as you keep assembly size under control, and do not intend to make drawings from those models.

  The model I linked above started out to be modeling practice, but then turned into an experiment to find out if Onshape would handle larger assemblies with complex 3d threads. I was truly impressed - but I don't advocate 3d threads for production work.