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.
Options
Speed when instantiating many parts
timo_schmid
Member Posts: 36 EDU
Hi everyone,
I have a featurescript which instantiates many parts and is therefore running slowly. I tried grouping the parts into closed composite parts, so instead of e.g. 1000 parts, I would have 100 composite parts.
However, this does not significantly increase the speed (neither the actual speed nor the calculated speed when profiling the featureScript). It actually seems to be even slower when using closed composite parts.
Does someone know why it doesn't instantiate faster, despite having much fewer parts? Or is there another way to make the deriving of parts faster?
Thank you,
Timo
I have a featurescript which instantiates many parts and is therefore running slowly. I tried grouping the parts into closed composite parts, so instead of e.g. 1000 parts, I would have 100 composite parts.
However, this does not significantly increase the speed (neither the actual speed nor the calculated speed when profiling the featureScript). It actually seems to be even slower when using closed composite parts.
Does someone know why it doesn't instantiate faster, despite having much fewer parts? Or is there another way to make the deriving of parts faster?
Thank you,
Timo
Tagged:
1
Comments
Website: ovyl.io
I think the reason it would be still running just as slow with the composite parts is that, internally, the parts are all still separate, and now you have given it more work to do, since it has to group the composite parts again.
What you could try, if the parts are touching, is booleaning groups of parts together, rather than using composite parts. Composite parts do not seem to be very much part of how Onshape works internally.
IR for AS/NZS 1100
What is the scenario - is it a single reference with 1000 instances or multiple references, e.g. 1000 configurations ? - performance of creating 1000 instances of the same reference is regeneration of source + pattern with 1000 instances, performance of 1000 configurations is 1000 regenerations of the source.
Do part studios you reference create only the parts you are instantiating ? - source regeneration regenerates everything.
Do you reference a part studio in the workspace or in a version? - reference in workspace means that every change in the source causes regeneration of the instantiating part studio, reference in a version can utilize caches better.
Thanks, I think this could be a suitable solution.
@lana
Thanks for the answer, I haven't tried referencing a verstion instead of a workspace yet.
I'm not sure I understand the question correctly. I have a feature studio with about 30 parts (in one composite). Then I instantiate it between 30 and 300 times, where some have the same configuration and some a different one. I don't know if it internally uses "pattern" for the ones with the same configuration..
Try optimizing the base part studio as much as you can.