Hi,
I have a parts with 500+ bodies and each approx. 30~35 MB large.
When i save to my personal network file it takes about 2:30 min. to save.
The rebuild time according to "feature statistics" is 1.81 sec. and when saving to my desktop it takes a couple of seconds.
Dragging the file to the folder on the network takes less than 5 seconds.
Saving to my PC and updating the files manually to the network isn't an option since i could forget this and/or make mistakes.
How can i improve the save times?
My specs.:
Solidworks 2014 Professional
Windows 7 Professional 64-bit
Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
Intel(R) HD Graphics (on board)
Ram 16,0 GB
Martin, that 35Mb file is a highly compacted set of data that mushrooms to hundreds of Megabytes when it's loaded and rendered to the screen.
When SolidWorks saves the file it has to repack all of that data, encode and compress it back into the file.
If you think about the model file as being analogous to a basket of laundry then you can see why it's quck to move it from one place to another. But just as you can't wear clothes that are still folded, SolidWorks can't operate directly on the data in the model file. So if the files are stored on your machine until they're transfered to your network, it's like folding your laundry right out of the dryer and putting it in your basket.
What you're in effect-doing is taking a handful of garmets out of the dryer, crawl through your HVAC ducts to your bedroom with socks dropping behind you, shirt sleeves snagging every corner and trying to fold them directly into your dresser drawers. You're going to work a lot harder and it's going to go slower.and bad things are going to happen to your laundry.
Unless you've got 10Gb switches and optical fibre, your network is much slower than your hard drive bus. Saving across your network is not only hard, but your inviting collisions, dropped packets and read/write conflicts to throw 'failed to save' errors, 'Pure Virtual Functional Call' exceptions and cost your hours of work or worse, corrupt your files. The best solution is to work on your files locally and let a PDM system take care of synchronizing them to a server.
You've got SolidWorks professional which means you have Workgroup PDM. Do the tutorials, set up a vault on your server and let that program handle transferring the files.
-and as a side note, that Intel HD chipset isn't suitable for SolidWorks. You're running a $5K program. Invest a couple hundred dollars in a Quadro K600. You will be so much happier with the result.