alexs0628
Computer
- Sep 9, 2002
- 4
I'm the IT support person. One of the engineers is complaining about how slow large assemblies open and close. (For example, One smaller assembly has about 200 files opening up from different directories and Solidworks makes temps of all of them in the network directories.) But the network tests out fine. He isn't using much resources on the net or on his PC and all other apps work fine on his PC, even while Solidworks is bogging down.(SW uses about 250meg of ram. There's 2GB of ram on the PC, with dual processors.) I have Cisco 3550 switches and a gigabyte pipe to the RAID 5, dual processor server. And there's next to no other traffic. Just him.(Only 25 users on the net. Very light-weight use by everyone else.)
It's seem like the more he works on an assembly, the worse the performance. I completely uninstalled SW from his PC. He was fine for about a week, then SW started to bog down again. He's the only one with this problem and it's with the assemblies he has worked on. Are there settings in his Solidworks that might be causing this problem? Or maybe the way he saves files when doing revisions? Should the temp files load on his PC and not the server?
It's seem like the more he works on an assembly, the worse the performance. I completely uninstalled SW from his PC. He was fine for about a week, then SW started to bog down again. He's the only one with this problem and it's with the assemblies he has worked on. Are there settings in his Solidworks that might be causing this problem? Or maybe the way he saves files when doing revisions? Should the temp files load on his PC and not the server?
![[pc2]](/data/assets/smilies/pc2.gif "[pc2] [pc2]")
