Do you have one or more miracle tricks to optimize the performance of Solidworks? Because indeed we manage large assemblies so light modes, complex assembly, low level of detail... but we spend a lot of time waiting in front of the PC (at the opening, at the reconstruction, at the recording...) I think that our network must have nothing to do with it. as well as the status of certain assemblies with over-detailed files from external suppliers or to imported files.
Do you know this setting, what do you think?youComputer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows GDIProcessHandleQuota set it to 20000
Do you have an opinion on the letter K at the end of the processor reference?
To check if it comes from the network you take a fairly large assembly, and you copy it entirely locally. If the opening time is x2 or more = network not great. If x1.2 to 1.5 = correct network. Several years ago, I had a long fight with the IT department, we had an opening time of x7... Following the visit of a network expert from Visiativ we now have an opening time of about 1.2-1.3. For complex assemblies, I find that this is worse than solved assemblies (faster to open but very slow with each reconstruction (so -Solved systematically) The opening time (in resolved) is certainly a bit longer but we gain a lot later for the modifications. For ideas, an assembly of + 50,000 parts can be opened in 10 minutes (with a much less powerful PC of + 8 years!) and a library with too many imports, not optimized as well. But the biggest win for us was the optimization of the network.
Edit: The letter K indicates the possibility of overclocking the processor. For the unknown parameter (for me) Edit 2: The high frequency of the processor is to be greatly preferred compared to the number of cores that SW uses very little. For me Intel Xeon at 3.6 Ghz on my old bouzin:
Hello; I agree with @sbadenis , the " Light " modes are not really interesting in terms of resource consumption compared to the " Resolved " mode. By the way, if you don't work on the assembly in question and you just want to " show " it to someone, I advise you to use Edrawing instead.
The points on which the impact has been significant on our assemblies at our company have been:
better management of antivirus (limit the scanning of the comings and goings of local files/servers and vice-versa)... if possible on all *.sld files *
Removal of Solidworks automatic backup options. (replaced by a warning after 20min).
all our templates are up to date with the Solidworks version used (document templates AND all our Solidworks files). …
Hi @Rems51 Simple: if Solidworks offers you to save it in the new version, it is because it was not already converted.
We are working on small assemblies but we have a PDM: the network is therefore much less useful since we work mainly locally. It must help a little on loading times (but the local view must be on a good SSD and not an old HDD in IDE...).
To have a few files donated by suppliers, my advice would be to do systematic analysis of all external files and simplify them (especially if they are files that are likely to be reused regularly on your designs). Casting parts with thousands of small leaves for example: if we repeat this kind of file 10x in our simple assemblies we end up with crazy latencies.
If you use BeneInox (and probably the same with others): hunt for their material extrusions with logo: the complexity of the part goes from 1 to 20 or 50 because of this kind of details (totally useless and which don't even exist in real life on the parts):
