AnsweredAssumed Answered

File Size and Cofigurations

Question asked by Ryan Beck on Jan 26, 2011
Latest reply on Jan 27, 2011 by Ryan Beck

I am trying to learn how SW loads files in large assemblies as it relates to memory.


In general, I have learned to use reduced feature configurations and found certain performance gains there.  I have also had limited succes with using SpeedPak in some cases.   Whichever method I use, there is a configuration that can be used downstream in larger assemblies that rebuilds and refreshes more quickly, but I am unclear as to how that loads into memory when opening a downstream assembly.


I am currently fighting a larger assembly that, when put into a drawing with a couple of Section Views, maxes out the available RAM and, eventually, the page file as well.  (I have asked to upgrade, but not holding my breathe...)


Has anyone else studied the effects of actual file size, regardless of the configuration used?  In other words, do the files loaded in memory consume the whole of file size, or does it restrict itself to the configuration size when loaded?  My past experience tells me that only the active configuration(s) is(are) loaded.


I wouldn't ask this if I weren't so buried on this one, and I am trying to get a better grasp on how to deal with this in larger assemblies yet to come... ...hopefully I can avoid creating small, unrelated reference parasolid files to maintain some semblance of appearances and bill items.