Fusion360 Running Very, Very Slow on a brand new Intel Xeon Processor W-2255 Workstation with 40 GB memory

Fusion360 Running Very, Very Slow on a brand new Intel Xeon Processor W-2255 Workstation with 40 GB memory

philspivey
Contributor Contributor
971 Views
9 Replies
Message 1 of 10

Fusion360 Running Very, Very Slow on a brand new Intel Xeon Processor W-2255 Workstation with 40 GB memory

philspivey
Contributor
Contributor

We've been running Fusion360 for a couple of years, got a new project and got a new Workstation to make sure we could handle it, spec is below. Fusion360 basically has become so slow it's unusable, checking memory usage we're up to 50% of our 40GB's, CPU usage can peak out around 78%, network and graphics seem to be low use but doing peak tasks we're in the "Very High" power usage.

 

Looking to see what we need to fix/upgrade ?

 

Intel Xeon Processor W-2255 (10C 3.7GHz 4.7GHz Turbo HT 19.25MB 165W DDR4-2933)
Windows 11 Pro for Workstations (6 Cores Plus) Multi - English, French, Spanish
40GB 1x8GB DDR4 2933MHz RDIMM ECC Memory
Intel NVMe PCIe SSD (Front PCIe FlexBay)
M.2 512GB PCIe NVMe Class 40 Solid State Drive
Nvidia T1000, 4GB, 4 mDP to DP adapter (Precision xx20T, 3650T)
 

Cheers,

Phil
0 Likes
Accepted solutions (1)
972 Views
9 Replies
Replies (9)
Message 2 of 10

g-andresen
Consultant
Consultant

Hi,

With which actions does the effect occur (sketch, pattern ...)?

 

günther

0 Likes
Message 3 of 10

TrippyLighting
Consultant
Consultant

You might want to share a model that exhibits that behavior.

The vast majority of Fusion 360 performance problems are not due to of lacking hardware.

 

Are the problems in the modeling/assembly area or in the CAM/Manufacturing area ?


EESignature

0 Likes
Message 4 of 10

philspivey
Contributor
Contributor

Unfortunately we can't share the model in question due to IP issues. We're seeing the issues in CAM, putting together tool paths etc We use Fusion360 exclusively for CAD and CAM and have not seen this level of instability, it's a complex model but not something we'd imagine is beyond what the software should be able to handle, we have dumbed down the model and that file suddenly corrupted last night and now we've lost that work


Cheers,

Phil
0 Likes
Message 5 of 10

philspivey
Contributor
Contributor

We're seeing massive slow downs in CAM, any toolpath we're creating, all of which are pretty simple 2D toolpaths, are taking minutes to resolve


Cheers,

Phil
0 Likes
Message 6 of 10

philspivey
Contributor
Contributor

We're also now getting Fusion360 crashing and corrupting the file we're working on so that it's unusable/unrecoverable


Cheers,

Phil
0 Likes
Message 7 of 10

ryan.bales
Autodesk Support
Autodesk Support
If you cannot share the model in the forum i would press you to create a case, chat or call with Autodesk to share the design. We cannot really do much without seeing the design. @seth.madore can take a look at it privately as can I if you still prefer to keep it in the forum. Just DM us the file or a link to it and we can take a look.


Ryan Bales
Fusion 360 Product Support
Message 8 of 10

seth.madore
Community Manager
Community Manager

@philspivey you could email me the file at:

seth dot madore at autodesk dot com

 

 

If I had to wager (without seeing the file), I'd suspect one of a couple things:
1) Massive amount of Pattern features. You wouldn't think it, but patterning a small island and a few holes over 1,200 times produces an insane amount of lag
2) Inserted SVG/DXF files that have an obscene amount of sketch splines and points


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 9 of 10

seth.madore
Community Manager
Community Manager
Accepted solution

I hate to tell you this, but performance isn't that sluggish on my end. Yes, it is a bit slow, but we're talking maybe 8 seconds to generate a 2D toolpath. I is annoying to have it slow at all, but given the amount of vertices on the model, it's not altogether unsurprising. 


Seth Madore
Customer Advocacy Manager - Manufacturing


Message 10 of 10

philspivey
Contributor
Contributor

We went back to the original model and started over, didn't cut and paste as that lead to corrupted files etc and now our performance is like you see, slow but manageable, so somewhere along the way something happened to the file but we have a "get around" now and know what we need to do to avoid the corrupted file. Thanks for looking into this for us.


Cheers,

Phil
0 Likes