Hi,
Has anyone had experience of this problem?
Open an assembly from the server. It maybe takes an average of 2 minutes to load. If I later try to open the same assembly but those files are open by another user(s) it is up to 5-6 times slower to load! Obviously, I will be gettting a 'read-only' copies of the files in use if the other user(s) has write access but why is this causing quite such a drastic hit on performance?
I have narrowed it down to this read/write access issue as if I set the Options setting to 'Load all referenced files as read-only' then the loading time returns to normal. This would be a pain in itself as you then have to take write access manually to each file that you wish to edit although it is a safer way of working.
N.B. We don't use a PDM system.
Any ideas?
Thanks,
Graham
Has anyone had experience of this problem?
Open an assembly from the server. It maybe takes an average of 2 minutes to load. If I later try to open the same assembly but those files are open by another user(s) it is up to 5-6 times slower to load! Obviously, I will be gettting a 'read-only' copies of the files in use if the other user(s) has write access but why is this causing quite such a drastic hit on performance?
I have narrowed it down to this read/write access issue as if I set the Options setting to 'Load all referenced files as read-only' then the loading time returns to normal. This would be a pain in itself as you then have to take write access manually to each file that you wish to edit although it is a safer way of working.
N.B. We don't use a PDM system.
Any ideas?
Thanks,
Graham
We had the same problems that you are currently having when all our data was stored on the network. It was a nightmare when opening large assemblies. I had our networks gurus do everything they could to maximize the speed but it was still slow. (Our network guys are really good too.)
I know you mentioned you don't use a PDM system, but we solved this problem by implementing PDMWorks Workgroup. By pulling all of our files from the PDMWorks Vault, it allows us to work locally. When you make updates to documents, you can check them back into the vault. If you already have SolidWorks Office Professional, you have PDMWorks.
Best Regards,
we have exactly the same problem. We have SW2006 SP4.1 and the file server is Windows2003 enterprise. Does someone know if this problem is still present with the newer version of Solidwork (2007, 2008) ?? Or if someone have found a workaround to bypass this problem??
Thanks