Hello.
For a few days now, I've had a temporary worker in the office, who also works on Solidworks. For the past few days, I've had a big slowdown in Solidworks.
So we came to the conclusion that our server doesn't like us working together on it. Has this ever happened to you? What have you done to overcome this?
I think it's PL who explains that without EPDM, when you work with several people on the same project it's "normal"
Hello
We also work together by opening the assemblies from the server. And we also have a heavy slowdown. From what I could see this is not really related to an overload of the server, at least with us the server administration console does not indicate that it is particularly busy.
I've come to the conclusion that solidworks doesn't like to work in a network... And I don't have too many answers to help you because I'm still looking for a reliable solution.
1. In any case, I advise you to always use the open file function and not to double click or make your file click in the SW window.
2. Preferably use a path with the ip address rather than a network drive e.g.:
- \\192.168.2.8\Business\Client\Study
rather than
- Z: client\study
One solution would be to use a PDM but it's expensive.
What do you mean by "PL"?
.... I understood, I had read a little too quickly...
Indeed, it's expensive. Especially since it's only for one month.
Well, we'll be patient I think!
PL is a forum user @gbadia
Yes unfortunately I think that for a month the easiest and to wait....
Personally, I have the impression that the more it goes on, the worse it gets!!
At home we have had SW for a good fifteen years and I have the impression that SW is getting heavier and heavier. Of course, many new functions have arrived but at the expense of performance for all basic functions.
Indeed, without EPDM you need a good server to send the data and even with a good server it is sometimes not enough torespondas and it happens to have crashes more often.
You're right, we the server and still quite powerful ert the workstations have 3 weeks it didn't solve our SW slowdown/crashing problem.
I think networking is just to be avoided when working with SW. Another element that can be a big problem is the analysis of the antivirus. When we had MSE (microsft's antivirus) we had to put the SW extensions in excluqion otherwise SW would crash continuously. Today we switched to Kaspersky, it's a bit early to have an opinion but it seems a bit less to leave the security active all the time.
Edit: by the way, if you call the technical support and tell them that you work in a network.... We'll quickly answer you that this is not the classic scheme that Dassault supports and that therefore they can't really help you. We will advise you to invest in a PDM .... that they have in the catalog of course!!
The same goes for the antivirus.
Big server at home and about 10 SW licenses on the server and quite regular crash even if much more stable than before. On the other hand, you just have to open locally to see a huge difference in the execution speed especially and also in the stability.
The improvements made
1- Antivirus disabled for SW file
2-Network card + 1 Giga memory power
3- no more ARm on PCs
But this does not solve everything, but improves
Hi, here are the solutions, after that it won't be miraculous either.
http://www.symsolutions.com/symblog/item/slow-solidworks-performance-on-the-network-speed-it-up
Are you in gigabit?
If you can physically bring the server closer (sometimes some switches limit the speed) and it is reserved for the BE it will be even better.
Duplicate
Well, gentlemen, I'm afraid I can't give any points to any of you.
In the end, I didn't feel good about making my manager buy an EPDM for 1 month. So I'm going to rummage through the options of Solidworks => collaboration => activate the multi-user environment and then all the options.
In fact, I think that the option "check if files opened in read-only mode have been modified by other users every XXmin" solves a big part of the problems. Solidworks must no longer make untimely trips to the server trying to save for nothing.
Finally, for the afternoon of Friday and for this early morning, it seems to be working well and making the difference. I keep my fingers in mind for the future:)
Thank you anyway for all your answers and the time spent
@PL: that's the first thing I did to blow up the switches. For server proximity, it's a little less easy