Does SolidWorks sometime feel like it’s working at a turtle’s pace? The problem might stem from being connected to a network!
Working on a network is great, and in today’s age it’s basically required. Unplugging from the network could solve a lot of issues, but usually isn’t feasible. The problem is that so much stuff is looking to the network it can sometimes slow down SolidWorks. There can be a ton of reasons for this, some can be fixed! Here’ are a few tips to make your performance a better while working with SolidWorks.
- Don’t work over the network!!! One of the biggest slowdowns you can cause in SolidWorks is by trying to work with files that are located on the network. If the files aren’t on your local computer, every time you open them, temp version of them are made in the directory they’re opened in. Every change you make has to get written to those. Every time you save the main files get written to. All of that going over the network is going to slow down SolidWorks. Copy files locally to avoid those issues.
- Backup/Auto-Recover: You should not have these locations be on the network. If these locations aren’t local, SW will again be constantly working and writing over the network and slow down. The backup option to put the backups in the same place as the original file can double the issue if you’re working on files over the network as well.
- SolidWorks Search: The SW Search is useful, but if you don’t use it, turn it off. If you do use it, make sure to set the indexing to “only when the computer is idle.”
- News Feed: Turn off the option in the general area of the options to “Show latest news feeds…” It may be minor, but it’s one more thing to slow down SW.
- Stop Streaming: Turn off things like streaming audio, unneeded web pages, and any other non-essential programs. The less trying to fight for resources the better.
- Stop the CPU War: Everything you’re running on a computer is constantly fighting for you CPU. When you’re on the network, even more things are fighting for it. If possible, dedicate a CPU core to SolidWorks. Windows defaults everything to the first core, once that’s full, it’ll start using other cores. Most of SW can only use one core, so the more it’s trying to fight with the slower it will run. If you can dedicate a core, it will reduce the chances of a slow down.
Trackback from your site.