Nearly reached my limit with Onshape

a_gore

Onshape has been getting slower and slower, maybe partly to do with my models getting more complex with configuration and the like I don't know but I don't do anything too clever or complex. I appreciate that the problem may not be with Onshape and that it could be my computer, browser, internet connection etc but if between Onshape and I we cannot resolve it Onshape is not a viable product for me and so far the cause remains a mystery.

Most of the time it can take me up to 10min to open a drawing, sometimes 20sec just to measure a line.

I find it annoying that Onshape come out with new features all the time but I have been waiting 7 months so far on a support ticket to fix a bug where I cannot delete an old configuration in an assembly otherwise the model won't generate, even though they are not assigned to anything. I now have loads of assemblies with config's that I don't want in them that I can't remove.

Anyway, rant over, I see many posts about people with speed issues but I have not come across any real fixes. I have tried different computers/devices and my internet speed is good. Does anyone have any other suggestions please?

Thanks
Pete

john_rousseau

Hi @peter_enderby. Sorry for the performance pain. Please open a support ticket. The speed of the service is not getting slower (actually, we really try to make it faster every release). Model complexity may be the cause or you may have run into something that we can improve. The support ticket is the way to figuring this out.

a_gore

Thanks for the reply John, I opened a ticket 16 days ago.

john_rousseau

Well that's annoying. I can't promise how fast we will be able to resolve other bugs, but having you suffer with a 10m open for 16+ days is unacceptable. There's a bug associated with your ticket that was marked as fixed 3 days ago. It's currently scheduled for deployment with our next production release. I am going to ask the developer and QA if the change is sufficiently tested and safe to push out earlier. Updates will be in your support ticket.

ilya_baran

Sorry about your experience, Peter.  I've been helping support figure out what's going on (with the performance issue) and there's one performance tip regarding configurations and assemblies that I thought was worth sharing broadly.

Imagine you have a configured part studio with several parts and several configuration parameters, and you want to use the parts from that part studio in an assembly.  It's really important for all the parts from that part studio to have the *exact* same configuration parameters, even if some configuration parameters don't affect some of the parts. 

Explanation:
Because Onshape doesn't know which configuration parameters affect which parts until it regenerates, we're forced to regenerate the part studio in all the configurations that appear in the assembly.  Because of how we do incremental regeneration and other factors, having even two configurations of a part studio can end up being much more than 2x slower than just having one. 

So if you're bringing in multiple parts from a configured part studio, use the "Select instances with same configuration" context menu option and make sure all your parts are selected.  And if your design actually requires different configurations of the same part studio, do your best to keep its regeneration time low (or even consider splitting into multiple part studios).

I realize that this is neither obvious, nor transferrable from experience with other CAD which do neither multiple config parameters nor multi-part modeling.

Hope this helps!

a_gore

Thanks guys, I appreciate the feedback. Improvements/fixes have now been made by the support team and the issue is getting better. I'll look at my configuration and see if I can make any changes with regards to what you've told me.