Sweep Calculation ridiculously slow

Sweep Calculation ridiculously slow

bschmu
Contributor Contributor
1,526 Views
10 Replies
Message 1 of 11

Sweep Calculation ridiculously slow

bschmu
Contributor
Contributor

I have a sweep which I didn't think was too complicated (path is 26 arcs) but takes over an hour to calculate out.  Is this issue software or hardware related?  In task manager it looks like fusion is only using 16% cpu and 1gb ram so I'm guessing its software related.

 

MS Studio

i7-6820HQ 2.7ghz

16gb ram

Geforce gtx 965M

0 Likes
1,527 Views
10 Replies
Replies (10)
Message 2 of 11

jeff_strater
Community Manager
Community Manager

share the design here, please.  Hard to say just from the description.  Regarding the CPU utilization, many geometry algorithms are inherently single-threaded. So, if you have a 4 core machine, the maximum CPU usage would be 25%.

 


Jeff Strater
Engineering Director
0 Likes
Message 3 of 11

bschmu
Contributor
Contributor

unfortunately I am unable to share my design.  I'll try to duplicate it in a way that I can share

0 Likes
Message 4 of 11

bschmu
Contributor
Contributor

Here's the link https://a360.co/3iEBpgs

0 Likes
Message 5 of 11

bschmu
Contributor
Contributor

@jeff_strater Were you able to take a look?

0 Likes
Message 6 of 11

jeff_strater
Community Manager
Community Manager

thank you for the reminder, @bschmu - this had fallen through the cracks in my to-do list.  I did take a look today.  It does seem like this is pretty slow for a sweep that is not all that complex.

 

I wonder about these curve segments:

Screen Shot 2020-10-13 at 5.25.17 PM.png

 

which come from these faces:

Screen Shot 2020-10-13 at 5.25.29 PM.png

 

but, that is just a theory at this point.  I will need to check with the modeling kernel team to see if there is something else going on here.


Jeff Strater
Engineering Director
0 Likes
Message 7 of 11

jeff_strater
Community Manager
Community Manager

we sent this off to the modeling so, what is this  team to investigate.  It seems to be a real problem, and we cannot find any problem with your design workflow here, at least so far.  Will update when we know something new.

 


Jeff Strater
Engineering Director
0 Likes
Message 8 of 11

bschmu
Contributor
Contributor

Thanks for looking into this!  Nice to know I don't need a new computer 🙂

0 Likes
Message 9 of 11

gulzar.dhanani
Autodesk
Autodesk

Hello @bschmu,

Are you still facing this issue with Compute All? If yes, then  please try the workaround mentioned below :

  • Edit the existing sweep feature through UI Timeline and click OK
  • Now do a compute all,  you can see the compute All is a lot faster
    Please refer to the steps mentioned below in the recording which shows how to the edit sweep feature through UI timeline.

    Sweep_EditFeature.gif

Please let us know if  you have any more queries?

0 Likes
Message 10 of 11

TrippyLighting
Consultant
Consultant

@bschmu did you build this natively in Fusion 360 including all sketches?


EESignature

0 Likes
Message 11 of 11

bschmu
Contributor
Contributor

Blast from the past!  If I remember correctly the design started in F360 with an imported 2d sketch dxf and built from there, completely in F360.  As mentioned in msg 6 above, that specific sketch was derived from faces.

Either way that project completed and I haven't taken a look at it in over a year so I can't say if the problem still exists and I don't remember what my solution was.