I started using Microsoft Task Manager the other day to see what was going on with SolidWorks after a program freeze and found some very interesting things were happening. I've tested this on two systems with different SP's of SolidWorks with the same results. I found that SolidWorks uses about 100MB when loaded. It grows when parts or assemblies are loaded. The interesting thing is what happens after laoding a decent sized assembly then open a small part and then close the part. The part can be one in the assembly or a seperate part. Major memory use drop ocures when the small part is closed. Eventually after working for a while the memory useage will grow and not be completely released as files are closed. Closing all files after a little activity still resulted in SolidWorks using around 300 MB with nothing open. I'm going to be opening and closing a small file after loading a large assembly from now on just to see how it effects SolidWorks usage during the day.
#1 Athlon 2200+1 GB ram 120 GB HDD Windows XP Pro SP 2.0 SolidWorks 2005 SP 1.0EV
#2 Athlon 2000+1 GB ram 80 GB HDD Windows XP Pro SP1.0 SolidWorks 2005 SP0.0
I'm monitoring the SLDWORKS.exe Process with task manager.
The sample assembly stats are as follows: Total components 1285 Parts 1175 Unique parts 439 Sub-assemblies 110 resolved components 1244
Results for SLDWORKS.exe process:
Start Solidworks 99,500K open sample assy 700,656K (reached over 800 during load) Open small part(89K) 710,584K close small part 142,644K
SolidWorks released 567,940K when closing the 89K part and still having the large assembly open. It doesn't seem to reach the big number again after opening and closing the small part. I'd rather start my day with142MB used instead of 700MB!! It's got to help stability and performance.