Tuesday, April 30, 2013

Free SolidWorks from Performance Constraints (FSWPC-13-#11)

(Modeling Methodology - SolidWorks Image Quality)


SolidWorks has the capability to display designs vividly with extremely high Image Quality and while this feature allows for a model with extremely high resolution, in general, they are not needed for everyday modeling. Higher Image Quality is intended to give better visual definition of very small components or components that contain very fine detail. The effect of this is a model that takes longer to calculate its visual data and a significantly larger file size. The former affects rebuild and repaint times while the latter affects model opening, closing, and saving. Both affect the amount of RAM required which amplifies the performance hit.




The best place to change the Image Quality setting is at the assembly level and selecting the option to propagate that through to all the sub-assemblies and part components as the Image Quality setting is per document. We have found that the sweet spot for this setting is around 25% up from the low end.


Also one item to note is that when you change the setting at a top level assembly it will adjust all of the part file but it will not adjust the sub-assemblies Image Quality level ony the parts in those sub-assemblies.


Note: This setting can have a larger or smaller on each users performance depending on how high their Image Quality was set.




You can by looking at our deltas see that on our Practical machine where we have enough hardware to support our model it added 15% to our benchmark. Where if we look at the Typical machine we can see that we pay the price for not having enough hardware to support our model set and it cost us almost 300% and took over 14 additional hours to run our benchmark.


Please
check back to the CATI blog as we will continue posting our
series of articles that goes further into the details of each of our tests. All
of these articles will be stored in the category of Free SolidWorks from Performance
Constraints
 and links to each with their
release date are listed below:



Thanks,


Josh
Altergott, CATI Support Manager


Adrian
Fanjoy, CATI Technical Services Director


 


 



No comments:

Post a Comment