AnsweredAssumed Answered

Cause of Performance Problem...

Question asked by Mauricio Martinez-Saez on May 18, 2008
Latest reply on Dec 8, 2008 by Simon Felix
We have ral powerful computers here... (Specs of one of our machine listed under my signature), and from time to time, suddently SW suffer a large degradation of performance (in fact the entire machine hangs)... we have beed looking at possible causes all over and suddently we found someting that can be the cause...

Every time that the performance of the software degrades, there is something that happen on the machine. If we take a look at the Windows Task Manager after the degradation of performance take place we noticed two things...

1.- The system cache memory allocation has gone well under the 140,000K when mormally on this machine it is at over 2,700,000K

2.- Solidworks memory use shows a very low figure on Physical Memory use (under the 110,000K) and a very large VM usage (well over the 2,000,000K) ans shows a very large number of page faults (over 2,800,000).

This only happen when working with SolidWorks, not with any other application.

Then if you try to continue working with Solidworks it will crash.... however if you stop working and let the applciation alone (loaded with the same assembly) and don't do anything with the computer in about 5 minutes, the Memory usage of SolidWorks start increasing and the VM Usage decrease a little and the application SW recover a little of performance, however if then you continue working the same thing will happen again.

At this point the only solution is to save the file (it will take a lot of time) and then close the application (SW) this will "release" the memory and the computer will return to work at its normal performance level.

Is this a problem with SW memory management? What is wrong with SW and the way he uses memory resources? So SW know about this problem? We have it for a long time... VAR's and SolidWorks indicate all cain of nonsense about video drivers, anti-virus, dust on the computer, etc, etc, but the fact is that the only thing we have detected is this problem with the usage of memory resources.

So some one has experienced the same problem? Try to open two assemblies not related to each other at the same time... or open a large top-down assembly and then open from within the assembly a couple of parts that are suppressed on the assembly and one of them is a mirror of the other, and then edit or create an eqution on one of the parts... you will see this happen.

We also believe that this problem is somehow related to the problem of the BUG on Switching from an open part or assembly to another open document (when SW show any file he wants even if it is not open) and the only way to switch from one open document to another is by using the Control-Tab or "browse open ducuments..." maybe when adding this new toy they create another "monster".

Any ideas abut any solution to this problem... it is costing us hours and hours of loss work.

M. G. Martinez-Saez
Director of Engineering, R+D and New Product Development
IMSA Group

SolidWorks 2008 x64 sp 3.1 + COSMOS Advanced Prof. Working on:

- Dell 690 (Build with true 64bit architecture WorkStation)
- Two (2) 80555K XEON DEMPSEY Dual core CPU's 5160 (3.2 Ghz, 2 x 4MB L2, 1333) Each (total of 4 cores, 2 cores on each CPU)
- 16Gb, DDR2 SDRAM FDB, 667Mhz ECC in Risers (8, 2GB DIMMS) RAM
- 786MB PCle x 16 nVidia Quadro FX4600 Dual DVI with SolidWorks Certified Video Card Driver (downloaded from SW WEB page)
- 1 - 150 GB / 15,000 RPM WD RAPTOR on SATA 0 for OS and Software
- 1 - 150 GB / 15,000 RPM WD RAPTOR on a separate SATA controller used EXCLUSIVELLY for the VM Page File - VM Configured as 300% of Physical RAM (48 MB) This drive also have a mirro copy of the OS for system recovery
- 2 - 250 GB / 10,000 RPM SAS HD's configured as RAID 1 No-Fault Mirror (Just for data files)

- Windows XP Prof x64 Ver, 2003 Sp 2.0

Outcomes