Slow Performance on Mac

[ferdyyy]

I am using an iMac Pro (3 GHz 10-Core Intel Xeon W, 32GB Ram, Radeon Pro Vega 64 16 GB).

On this machine I get great rendering times but other than that the performance of Fusion 360 doesn't seem to be that great. I experience:

• Long closing and opening times (and sometimes freezes during closing)
• Slow compute times on things like offsetting face (because it is editing some previous step I guess)
• Sluggish View Responsive (panning zooming etc.) including the scrolling of the timeline
• Slow recomputing times after editing old steps in the timeline

Here is a folder with a few videos showing the performance issues I mean (PERF_*.mp4)

https://www.dropbox.com/sh/gq4mkp8i0m66qgo/AABRbQ7Nj3iXrHvaMNZqNtjRa?dl=0 

Moved from another post: @Phil.E 

[Phil.E]

Thanks for taking the time to put this all together. I have to break this down for clarity.

"Bug Body Gone" - What happens when you use Compute all, rather than "get all latest". I'm curious if the body disappears because of compute (which happens when you get all latest). In any case, I need a copy of the design to debug it and find the problem.

"Perf calculating offset error" - What happens when you try to do the same operation while not in the rendering environment? Is it any different if you use extrude instead of Press-Pull (or Offset Face)?

"Perf closing taking too long" - It's really hard to tell what's going on when your camera is zoomed into such a tiny portion of the screen. What is quite clear is that you used force quit but did not send in the crash report. Did you close Fusion soon after pressing Save? If so there should be a dialog box that appears to tell you Fusion will close once the save is uploaded to the cloud.

Just a word about crash reports: I monitor CER (crash error reports) but I can't monitor reports that are never sent in. If you crash repeatedly it's more important to send in every report. Repeated crashes means "repeatable problem" and this gets my attention very quickly. No reports, no attention.

What is your internet upload speed?

"Perf sluggish timeline" - I see no problem. That is the scrolling performance of the Fusion timeline, not specific to mac. What exactly is the problem you find with this? Please describe how that impacts your workflow.

"Perf start up" - That is exceptional start up time. Fusion went from "open" to "in use" in 29 seconds.

One question, I noticed you have some addins installed. These can sometimes affect performance. Can you give a screenshot of your addins dialog so I can see which ones you have installed?

I'm glad to work on any of your concerns here, but I think going forward a few things might help.

1. If you have a strange issue like the body bug, a model is essential. If you don't wish to share on the forum, you can send me a link privately.

2. If you use Autodesk Screencast it records your keystrokes and has voice recording. It would be a lot more informative to see videos made with Screencast. 

Thanks,

[ferdyyy]

"Bug Body Gone" - I made a new post about that: https://forums.autodesk.com/t5/fusion-360-support/bug-updating-component-removes-completely-unrelate...and I actually found out where the issue lies.

"Perf calculating offset error" - When using in Design instead of Render environment it is the same. When I use Extrude instead of Q (Which defaults to Pull) then it works fast since it doesn't have to edit a step back in time.

"Perf closing taking too long" - "Perf Not Closing" - "Perf Not Closing (No Add-in, Activity Monitor)"

1. New Videos: I added two new videos, now screencasts ("PERF - Not Closing" and "PERF - Not Closing (No Add-in, Activity Monitor)"), but you can't see the beachball here. It start's at around 0:43 and 0:37. I waited for it to upload first and then tried to quit Fusion 360. In the second video you can see that Fusion is drawing 100% CPU on one thread, I'd say it is a loop but that's a bit generic and I am really no expert.
2. Add In: The Add-in was USDZ Exporter, I uninstalled it and got the same problem.
3. Error Report: In the new videos I didn't force close and just ended the screencast before. I normally never send reports after force quitting the application because I always thought the error report won't be of much use to you if I deliberately do so, is that assumption false?

"Perf sluggish timeline" - Ah okay didn't know that. Using a Mac and a Magic Mouse (no scrollwheel stops) I am used to buttery smooth and snappy scrolling.

"Perf start up" - Yes you're right this was just in there for reference, that's why I didn't mention it in my post.

• Regarding the model link, here it is: https://a360.co/32itqRH
• Regarding the screencast: Won't do much when closing the application, because it is built into the application I am trying close right? I attached normal screencasts though. If I should comment on what is happening I can do so as well.

Thanks a lot for your engagement and help so far.

[ferdyyy]

I forgot the internet speed, It is around 210 MBit/s Download and 13MBit/s Upload.

[Phil.E]

Thanks for the model.

The raspberry assembly explains a lot of your experience. It contains:

• 297 out of 312 components 
• 1251 of 1477 total bodies
• 32.83 MB

It is also extremely detailed. Just a sample: This connector alone has about 4 thousand edges.

There are 779 objects 1mm or smaller on the board. Mostly these are surface mount solder joints like you see here.

One suggestion would be to reduce the complexity of this circuit board assembly. Unless you need it for rendering, those thousands of tiny details are only hurting the performance. 

Thanks,

[Phil.E]

I should mention I tested "save on close"

• Windows 23 seconds
• Mac 39 seconds

If you see much longer times than that, please collect your logs and post them here.

[ferdyyy]

For me it is not closing at all unless I kill the app. 

[ferdyyy]

I will definitely try to get rid of most of the small resistors and so on. Thanks for the suggestion.

[Phil.E]

When you force quit, do you get a Fusion 360 crash report dialog? Please send those in. I can't find any reports from you that indicate force quit. Always send in every single crash report. There is no way for me to track customer crashes if I don't know they are happening. 

[ferdyyy]

Alright, didn't know those crash report would carry any data of interest if I deliberately crash the app. But will do so in future.

[Phil.E]

Just the fact that you feel like Fusion is crashing, even if Fusion is just computing a massive edit and is unresponsive for a moment or two, is worth sending in the CER. Thanks.