Is there a limit to the number of features in any one part studio before performance falls off?

npennycooke

I have a part studio that has a large number of parts, and a larger number of features (since the only way to reference other parts is create them in the same part studio), and it's at a point where I can't work on it anymore. It takes about 20-30 seconds between, for example, drawing a rectangle and being able to interact with it or constrain it in any way. For every single operation, the spinning clock in the corner comes up causing something that should take only a few seconds require several minutes to complete. Even pressing 'N' to shift to a normal view can take upwards of a minute.

In other part studio tabs, things move quickly as expected, without any hiccups. Is there a limit to the number of features OS can reliably support in any one part studio? If so, why not allow users to edit parts in the context of an assembly studio so that one part studio doesn't have to be loaded up with hundreds of features for parts that require references to each other?

Is there any way to alleviate this?

npennycooke

Just to follow up: I've now started getting "Resource limit exceeded" errors.

lougallo

@npennycooke Can you send us a ticket?  ? menu -> Feedback and send us a screenshot of this?  We can look in the logs and see what you might be experiencing.  We would like to see what limits you might be experiencing and see what we can do about that.

jakeramsley

npennycooke said:

If so, why not allow users to edit parts in the context of an assembly studio so that one part studio doesn't have to be loaded up with hundreds of features for parts that require references to each other?

The short answer is that we are in beta and that there is functionality that we know we have to do but haven't had a chance to finish and productize them yet.  It isn't a conscious decision to not have in-context assemblies, but that we are iteratively building a product and that it is expected to be future work.

billy2

Can you take a snap shot and post an image of your project? It'd be nice to see if it's bigger than a bread box.

I've been working on this mold base inside OS (259 components).



So it's fairly good sized model:



This file came across as a parasolids and there are no assembly structures, it's just one large part studio.

Both SW & OS struggle with this file in it's current state and I'm breaking it down into groups/sub-assemblies to manage the data I can show on my screen at any one time. This will make this manageable.

Instead of forcing the CAD system to display everything in my design, I tend to work on strategies that'll allow me to make things go away and come back. I want my system to be responsive and tend to organize my data into manageable chunks that I can turn off/turn on. At the end of the day when I want to print out the overall, the system takes more time to render.

Knowing how 3D CAD works helps when designing large assemblies. There's 2 parts to a CAD system: the display, the geometry. That pretty shaded image you look at takes 50% of resources. Geometry creation occurs during a rebuild (and on a server in OS), the rendering of your design is done on your computer. Rendering is done both on your CPU and graphics card. Rendering is a big deal for OS (all CAD systems).

The image is based on polygon count and being mindful of this can really help your large assembly performance. Having configurations containing simplified representations of parts is a good strategy to manage  your display (can't be done in OS). I tend to just delete unwanted features that cause high polygon counts (can be done in OS). In my assembly above, they used Mcmaster Carr bolts with helicoil sweeps all over the place. Helicoil sweeps create a high polygon count to represent a bolt. I usually extrude a cylinder over the Mcmaster Carr sweeps to reduce the polygon count. My first group that I created contained all the bolts which I hid. The system became extremely responsive after turning these off. 

The time to open an assembly is based on the display list coming over the internet. Keeping your polygon count down will help. Understanding your geometry will help in that a plate represented by 6 analytic surfaces and 12 polygons renders in no time. Rendering a helicoil sweep takes a lot of resources and to represent a bolt, to me, is a waste of time. I back out all of that stuff from my designs to keep things responsive.

I've played with many large assemblies in OS looking for ways to setup means to manage the datasets displayed on the screen. I like it, I can reduce and manage what's on my screen easily. I don't see this as an issue after setting my large assemblies up properly.

I'd be interested in your design, if you can share an image I'd be happy to offer my suggestions to manage it and make it more manageable.

npennycooke

@lougallo I've run it down and it seems to happen when I have two OnShape windows open, when trying to work in a part studio in one window and looking at the assembly studio in another window, and only if the part studio open has a long feature list. In this case, the assembly studio was from another branch of the same document. If I have a simpler part studio open, I don't get the slowdowns. If I have two assembly studios open, no slowdown either. Only when one is the feature heavy part studio. The Resource Limit Exceeded error comes seemingly at random times so it is hard to replicate.

Since I've started working on it again this morning, I'm not seeing the slowdown at all. What I'll do is keep both open for most of the day and see if it gets progressively worse (likely pointing towards a leak issue). If it does, I will submit a ticket as I see it.

@jakeramsley Understood completely. I should have framed that as a suggestion and not as "why isn't this in yet". Excited to see where things go from here.

@bIlly Unfortunately we can't post up images of the project on the public forum right now. When it comes to rendering, I don't have any unreasonable hiccups with panning/rotating or model display. It's only when I try to do an operation such as sketch/feature creation or measuring a line or distance between planes. Over the past few weeks I too have been breaking things down into more subassemblies to manage things a bit better, and that has helped make it easier to work in assembly studio. I'll definitely keep these things in mind as the assembly grows and when we move on to other products.

npennycooke

Update: Got the resource error again, captured on Friday. This time with only the part studio opened, but right after trying to complete a boolean operation.

AnotherOnshapeUser

I have had two major crashes where I lost around 100 hours of work from having too many features in a part studio. Fool me twice, shame on me...no more than 250 - 300 features is safe.

nick_papageorge_dayjob

AnotherOnshapeUser said:

I have had two major crashes where I lost around 100 hours of work from having too many features in a part studio. Fool me twice, shame on me...no more than 250 - 300 features is safe.

How did you lose work? Can't you just go back a version (or micro-version). In 2 years of using OS at my dayjob I never lost a single thing. Yes, sometimes the system hangs up, but never any lost work. Super curious how you could have lost 100 hrs of work?

Also to close the loop on the original topic of this thread, there is in-context editing for a few years now.

nick_papageorge_dayjob

I've gone up to about 600 features. It was quite slow. 300 range seems safer for decent speed. It also seems to matter the types of features. If there are patterns for air vent holes, for example, that can slow the studio to a crawl even if only 100 total features, since the pattern is only one feature. Derives are slower features than regular features because they inherit some of the speed of the parent model. I've also noticed sheetmetal models with many holes/cuts slow down a ton. Its a cumulative effect. Also system ram definitely seems to help. Some of the slowdown is on the servers, but some is also local performance when there is a big model. That's been my experience.

I've worked in proe carseat models that had 4000 features. To regenerate that whole model took forever. But, once regenerated, working within a feature (the sketch) or creating a new feature is normal speed. OS is definitely different in that regard. When it starts to slow down, everything seems to slow down, even brand new super simple features.

I've contacted support many times for help in speeding up my models, and they were always super helpful and had good suggestions.

S1mon

One thing that I've seen in Solidworks and Onshape (both Parasolid kernel), is that if you have a body with a complex shape and you keep adding extrudes or cuts which intersect with that complex shape, it gets very bogged down. If it's possible to build a bunch of ribs and bosses separately from some ID shell and then do one big feature which puts the two together, that might help. Also lots of draft and rounds can really slow things down. I never model tiny external rounds on internal features of injection molded parts unless they really need to be there.

dirk_van_der_vaart

If your getting to much features on a part in a Part Studio you derive that part to a new Part Studio and add more features to the part.