Peter De Vlieger wrote: ↑Thu Dec 15, 2022 4:16 am
Frederik,
Correct me if I'm wrong but unlike a database, where the program can do a query on a database and there for only load bits and pieces of the database instead of the entire database, Solidworks loads a file completely. Or in other words, a file of 50MB when accessed by SW means a minimum of 50MB is transferred.
"One size doesn't fit all"
Best is load everything into memory because the program will run faster, if there is enough RAM to load everything.
(You are complaining about file size, other are complaining high RAM use, high CPU use. That's another story
![lets watch **](./images/smilies/popcorn2.gif)
or two)
To keep the program responsive, it need to load as much into RAM as possible.
The faster and less files to look for those info, the faster the program become responsive.
Since everyone was complaining SW was slow when loading large assembly and drawing, something was done to make it "faster".
That "something" is put some of those info in assembly and drawing file.
Every time a model is loaded, SW (or any CAD) need to calculate how to display it on screen. It is slow.
So some of the result is saved in part file, assembly and drawing. So user can see, zoom and rotate the model. Before everything is loaded and calculated.
Those "extra" info are not really extra. They were calculated before. Now they're saved and reuse so user don't need to wait a minute.
So actually even file size increased, nothing more was added to RAM. They are there a minute earlier.
SW became a time machine
Lost track of my thought, I'll be back .....