Aside from ensuring that all of your specs meet SolidWorks recommendations, have you considered what impact each component or assembly may have on the 'final' assembly? Design intent and workflow could have a big impact on resources when everything comes together. Obviously it is unknown to me whether all parts were created by one user or several. Were they created in such a way that they had the smallest impact on resources? If you are confident that this is indeed the case, then perhaps look at your machine hardware.
Many sub assy, such as : body hull assy / power pack assy / electrical harness etc, design by several user.
But final assy will design by one-user, who combine those sub-assy to ensure, who will place what in the vehicle.
So.... we will know :
- the space requirement in that vehicle
- the total gross weight
- the centre of gravity
We have 5 SW Premium 2017 licenses ( include 5 HP z240 workstation ), and will expand about 6 more licenses.
What version of Solidworks are you running and with what OS?
Getting a newer, younger, graphics card would be my first thought, even before adding RAM seeing as that you already have 16 gig.
How much of your RAM does actually get used while manipulating and working with that model? If it doesn't go above 70% then it seems only logically more RAM won't help.
We run on SW Premium 2017 sp5 64 bit.
We had apply Large Assembly mode ;
- turn off Realview
- make auto Lightweight Assembly while open
- turn on auto Purge memory while close
Sometimes crash while out of Memory, but it ussually happens when we open any step files about over 100Mb of rolling chassis / engine surfaces.
But make a final whole vehicle, it will slow & heavy.
I would suggest making many subassemblies of associated parts (maybe passenger door assy, etc) and then combining them to form the top assy. Each of these subassemblies could be set to use large assembly mode and large assy design review mode to speed things up.
The processor is very critical and the one you have seem decent to me while your video card is a low end one
There are many things to consider such as:
1) tell us about 6,000 parts: how many hardware or standard parts you have in the assembly? are there many sub-assemblies in the main assembly? how complex parts in the assembly (run the performance evaluation to see how much time to rebuild the part
2) are there many mates in the assembly? The sub-assembly are rigid or flexible
and other things which you need to tell us how you built your assembly which cause the issue of loading and executing
1). Standard parts were:
- bolt & nut
- automotive components ( mechanical & electrical )
There were many sub-assy ( steering/breaking/doors/suspension/body hull etc )
2). Main assy will take a rigid assy, b'cos we delete all mate & going to FIX all components.
Any simulation of movement will just took in a sub-assy, not in main assy.
All advice above is sound, I also recommend a larger quadro video card. Used from ebay has always been a great solution for me.
Get a really reliable and fast network!
My first thought when I saw your post was, are all the files local on the Workstation computer or are you loading them from a network or PDM system that is on a different computer.
If they are on a server (or different computer or PDM than the workstation you are running on), make sure you have a high speed Network (as Ryan McVay has said). Also, if on the files are on a server, how fast is your server?
All the replies above are things that could slow down the assembly and if you put several of those conditions together it could get really slow.
Also, do things like, don't use Real View Graphics, make sure that each individual part or assembly does not have any rebuild errors or problems or warnings - if they do, fix the part or sub assembly before bringing into a larger assembly.
Do a Ctrl Q rebuild on each part and sub-assembly before you save the files to make sure the files rebuild correctly and efficiently before save, so when they are brought into your assembly they don't bring in any problems or needs for rebuild.
For now, the main assembly come in the local single workstation, while sub-assy come from the others workstation.
Then, we collect all sub-assy & combine it to be a main assy in the single workstation. ( we have 5 workstation ).
Unfortunely, we didnot use PDM standard / profesional yet.
We though to begin use it now, is it will make any better solution?
Btw, about any errors/ warning, sometimes we get that, while we receive step / iges file from engine manufacturer.
Some part produce error/warning/ yellow marks with blank note, so we didnot ensure what kind of error of this part.
It was a standard component, so we didnot want to spend many time to fix this kind of error / warninng.
Sometimes, main assy comes with yellow markings
I think the Video Card needs to be upgraded.
I remember watching a great presentation from Alin Vargatu at SWW2017 on this. I don't know whether you can find it online or maybe he can give it to you? If you look at opening times alone to start with there's a set order which SolidWorks follows to open the file and various aspects such as the media which the files are stored on, external file references, mates etc in which it tries to solve the assembly.
The long and the short of it was that you should aim to be storing the files on SSD media, (Or use a PDM system to create local cached copies on SSD's), try to avoid external file references where possible and fix issues with mates and geometry that SolidWorks might try to rebuild twice to fix.
Using some of these basic principles we are able to open our ~2000 part assemblies in sub 30 seconds even on workstations not supported on SolidWorks.