I have a part that was 25 MB. Each time the part is saved, with changes, the file size increases by 25 MB. It is now over 500 MB and continuing to grow. How do I fix the part file, and how do I prevent this?
Welcome to the forum. What kind of part are we talking about?
Can you post it for us to look at?
I cannot disclose the part file. It has a large number of features and patterns, but the file size was maintained below 30 MB. We recently upgraded from SW2010 to SW 2011, and converted this file. The issue may have begun then.
How can you view the properties of a .sldprt to see if it contains any old versions, or copies of other files?
If you do a File->SaveAs to a different name, does the size remain at the 500 MB or drop back down to 25 MB ?
I understand. I was just going to see if this can be duplicated on another machine.
Is everyone where you work experiencing this?
I am not aware of a method or program that looks into the file like this.
Unlike Pro-E or Autocad, Solidworks does not have a purge command.
I was told that 2011 is supposed to be better at managing file structure.
Meaning it is supposed to release unused files out of memory.
But this is not what you are experiencing.
I was just wondering if you had excessive cosmetic features like threads,
The file size dropped to 485 MB. There are no cosmetic threads, and only one small text feature. Is there a way to purge any unnecessary references or data from a .sldprt?
Brian, are you adding more features or just saving it is increasing the size. Is your part symmetrically??
SolidWorks doesn't really hang on to unnecessary references when you do a save. This ever-increasing filesize behavior seems like a bug. You mentioned this data is confidential, but you should be able to report this issue to us through your VAR and get an answer on what's going on fairly quickly.
You can use EcoSqueeze to reduce your file size. It has various options, from mild to radical. You can download it from the developer's site:
The milder squeeze won't reduce it any more than your save as did.
I'm suspecting that you are using SolidWorks 2007 SP2.1 or older (maybe even SolidWorks 2006) on an XP system? If this is the case, MicroSoft had a bug that caused SolidWorks files to grow rapidly (double in size each time they were opened and saved). If this is the case, then upgrade SolidWorks.
Follow me on Twitter
he stated in one of his posts "We recently upgraded from SW2010 to SW 2011" so he is on SW2011.
Also, there is another post titled "Part file size has grown" in this section that is along the same lines as this. I am experiancing this problem as well on a part I am working on, see the other post for my comments there.
Try the macro Charles has shared in this post: Re: Really really large slddrw file
Seems like this is a growing problem (no punn intended)
Here is the reply I got from our VAR on the issue.
The root cause of this is the same as SPR 549188. Inside these files – there are thousands of redundant and corrupt display entity objects. This is the reason for the large file size.This issue has been resolved in 2011 SP3.0 (released in next cpl of weeks)SP3 will have a new RMB menu item for display states which says “remove all display states” though this isn’t desired in most cases, in extreme cases like this, it is needed to purge out all the display information which is causing the problems. Please see attached ZBRSL12_R.zip Using the above new option and resaving in SP3 I was able to reduce “ZBRSL12_R.SLDPRT” from 181+ MB to 3.9 MB.This message is from SolidWorks I did not attach the file since you have already redrawn it.
It appears there is an issue and it's getting fixed, or at least getting a work around.
I'm running SW2011-SP3EV but don't see the RMB Remove all Dispay States option.
Solidworks files have tons of wasted space. The data structures are very low density. There is a bunch of useless crap. The files contain references to features deleted long ago. There is a reference to every version of solidworks that may have edited the original file. The features are in a very sparse database that is mostly useless. There are many 256 byte blocks that contain the alphabet. Operations on features are spelled out in 16 bit ascii, in a block of 256 bytes of "FF" or "00"
You should look at the content of a Solidworks file.
The essence of a Solidworks part can be perfectly represented by data 1200 times smaller than a Solidworks file.
The macro, SPR341510, for SW2007 works, and avoids the file size doubling at every save. The solidworks part data structures are bulky, inefficient and wasteful. I want a 1200 times smaller file.
Why do these really troublesome bugs not get detected? It is not that hard to look at the part data file. First flush the crap, then compactly encode the features, sketches and relations. Add some display fluff and a 3d preview. If it were encoded properly it would be 1200 times smaller. This compact form could be readable by several versions of SW.
Yes I have a hot button regarding file sizes because Solidworks claimed that the larger file size increased performance. I believed it for years, until I looked at the file data. I regenerated a part and noticed that the first rebuild took no longer than subsequent rebuilds. I then calculated the data required to represent every feature, sketch, relation and property. SW files are 1200 : 1 fat to muscle. Some of that fat is gross bugs hidden in fat.
What I'd like to know is if they plan on fixing this in any of the other versions. Although I have the subscription service to receive new versions, and have 2011 sitting in my desk, I can't upgrade to it yet because of vendors I work closely with that are still running 2010.
You need to go to the configuration tab, mak sure you have not selected a display state and RMB in the display state area.
Just want to add my name to the list of those having problems. Several files went from 3Mb to 52Mb to 99Mb ect...
In the earliest days of SolidWorks, the model files were actually a macro file. The file size was very small back then, but opening the file actually would run the macro to reconstruct the model. Back then though SolidWorks only had simple extrusion feature, so reconstructing the model did not take that long.
I am having the same problem with a file. It is a very simple sheet metal extrusion. It started out as about 200k and each time it saves it increases in size. It is now over 80meg. I decided I can't wait for this file to keep autosaving...soooo i made a new file and it did the exact same thing. Then I started deleting different holes etc and it still increased. Now I am at the inititial profile and still gets bigger. So I decided to take the profile and just extrude it as a simple extrusion (non sheet metal). The file is less than 100k and and has not increased.
I have the same problem, file increasing from 15Mb up to 80Mb.
Sent this to my VAR who sent it to SW, here is their reply:
There is a problem at present where we are seeing bloated display state data in some parts.
This has been reported to our development team in SPR548472 and they are now trying to resolve this.
You will be notified when this issue has been resolved.
In the mean time if you encounter this kind of problem please try to delete the existing display states from the file. If the option 'link display states to configurations' is selected please uncheck this and delete all the display states. In SolidWorks 2011sp3 that is due for release soon there is an option that can be accessed from the RMB menu of the Display State section of the ConfigurationManager that will automatically delete all this data for you.
I have modified this file for you and attached it to the SR.
Unfortunately the workaround required that I remove the customers display state information from the part but they will be able to work with the part more easily now.
The file that was sent back is 10Mb! Incidentally I was not using any display states other than the default and unchecking 'link display states to configurations' made no difference. Looks like a regression in 2011.
Lets hope they publish a cure.
I managed to reduce the file size of some of our customer parts by doing a "SaveAs" in a different location (with the same name) and the file size dropped from 90MB to 6MB. This hasn't worked for all the files that have excessivly large file size but it worked for some.
Note: It seems like there are two different issues going on. The files that were under 100MB were fixed when doing a "SaveAs" but the files that were much larger (200-300+MB) were not effected by doing a "SaveAs".
Edit: After opening up multiple configurations and saving the file size is increasing again. There are 30 configurations in the part and after opening 1 new configuration and saving the file size increases by 2MB. After all 30 configurations have been opened the file size is about 58MB, but if you do a "SaveAs" the file size is again reduced to 6MB.
Retrieving data ...