I am running a new Dell laptop with an i7 and no dedicated graphics. Everything on solidworks is extremely slow. How could I solve it? Thank you!
Typically this is caused by two things.
First is that you are not running the certified video driver for your system's setup, please verify that here.
Graphics Card Drivers | Hardware & System Requirements | SOLIDWORKS
The other is corrupted user settings imported from another system with mapped drives or network locations in the file paths. You can test this my temporarily resetting them by following the steps below.
SOLIDWORKS w/o PDM:
- Close SOLIDWORKS
- Open the registry editor (regedit.exe)
- Locate the following key: HKEY_Current_User\Software\SolidWorks
- Right-click the folder and select Rename
- Add a ‘_OLD’ at the end
- Launch SOLIDWORKS and test
SOLIDWORKS w/ PDM:
- Locate the following key: HKEY_Current_User\Software\SolidWorks\SOLIDWORKS 20XX
- Launch SOLIDWORKS and test
**To reset the user settings open the registry editor and hit the F5 button. Delete the new HKEY_Current_User\Software\SolidWorks or HKEY_Current_User\Software\SolidWorks\SOLIDWORKS 20XX folder and rename the one with the ‘_OLD’ at the end back to SolidWorks or SOLIDWORKS 20XX**
I followed these steps but it didn't quite change anything...
I passed my benchmark CPU:1.8secs IO/S 37sec Graphics:130secs. My computer is a Dell XPS13 with IntelHD 620 graphics, are these graphics results unusual in this computer? Thanks alot!!
Jeff, I know that this post was a year ago.....
But I was wondering if you could explain further this statement:
"...with mapped drives or network locations in the file paths"
Are you saying that the mapped network paths are corrupt, or that having mapped network paths is bad, or that the user settings are corrupt?
I'd like to know this too.
I found that Quick Access is A Bad Thing somehow. I disabled mine and my slowdown got better
There are a few things that can slow a system down using mapped drives (this is at least my understanding of a mapped drive - but I am no expert on it).
First you are going to a drive that is external from your system. This means that you are not directly connected to your computer hardware which is more efficient communicating to the internal drives - better speed and data transfer rates.
Mapping a drive "Simulates" an internal drive with the file paths. But the drive can be anywhere from next to your computer to the other side of the world. You have Network speeds (slower than your internal system data line speeds), Cables that may not transmit as fast depending on type and length (Cat5, Cat6...), Network traffic, Network connection devices in the flow, the computer that is holding the mapped drive may be slower, overloaded with incoming / outgoing data requests, the mapped drive itself may be older and slower, mapped drive may be segmented (not defragmented).
All of these are possible things to slow down the data transfer.
This does not mean that they are Corrupt (but they could be - the same way your internal drive could become corrupt). There are just more things in the loop that can slow the data transfer or cause loss of transfer or slowdowns.
It is most efficient to have your data on your system IF your system is a fast system with good drives.
The good side of a mapped drive is that it is (Usually) setup as a central location (or server) for data that all users can access like it was on their computer. Also, servers are often backed up more often than individual computers. For a single user it will usually be slower because of any of the things I have listed above but for groups it is usually better (but file management system is more important.
This is also why the recommended way to work on files is to copy them to your local drive, edit them there and then upload back to the mapped drive where everyone can access them. If you are sharing files, then you should have some form of PDM so that a file is not downloaded and edited by several people at once and then uploaded and overwriting someone else's updates.
There is also more to it but these are the main points.
Generally, the previous responses to the OP are dealing with the actual workstation setup - but if a mapped drive is added to the mix it can cause the slowdowns with all the reading and writing - that is why it is recommended to copy the file(s) to your system, work locally, then upload them back to the mapped drive. If you see no improvement working locally vs. working on a mapped drive then the problem is in the workstation.
I would like to recommend you run a Benchmark test and see if your CPU/Graphics/IO readings are comparable to others with simular hardware.
I passed my benchmark as told, my times were: CPU:1.8secs IO/S 37sec Graphics:130secs. My computer is a Dell XPS13 with IntelHD 620 graphics, are these graphic results unusual? Thanks alot!!
I think IntelHD 620 graphics card is not recommended by SOLIDWORKS.
Retrieving data ...